# Get More From Testery

You should be up-and-running now, but we're just getting started. To get more from Testery, you can:

* Set up [Environments](https://docs.testery.io/get-to-know-testery/set-up-your-test-environments) so that you can run tests in different environments and pass in environment variables.
* Set up [Alerts](https://docs.testery.io/get-to-know-testery/alerts) so that your team will get notified in Slack, OpsGenie, etc. when test runs complete or fail.
* Set up [Schedules](https://docs.testery.io/get-to-know-testery/schedules) so that test runs will run automatically either on a schedule or on every deployment.
* Follow the [CI/CD Integration Guide](https://docs.testery.io/integrations/ci-cd-integration-guide) to set up you build server to run tests on the Testery platform.
* Check out the [Testery CLI Docs](https://docs.testery.io/integrations/testery-cli-docs) and [Testery REST API Docs](https://docs.testery.io/integrations/testery-rest-api) to build your own integrations. Be sure to let us know at <support@testery.io> what you come up with!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testery.io/get-started/getting-started-guide/create-schedules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.