> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/administration/deployment.md). # Deployment ## What is Deployment? **Deployment** holds all the target environment details, like Sprint, Staging or Prod environment. The test execution can be performed on one of the deployments. ## Example for Deployment To know how Deployment works. To clearly understand lets get into a example.‌ An Organization having a QA Team and Developer Team, both the teams will be running their work on same Websites. A changes made by developer team on a website will not be affecting the work done by the testing team website. There will two separate versions of website will be maintained.​ ![](https://gblobscdn.gitbook.com/assets%2F-MgdWk21zETVSCGfZEts%2F-Mgl-_81dDSSg5ka4-8W%2F-Mgl0LwVU45veaekM1--%2FDeployemnt.png?alt=media\&token=4edecba5-7a14-4044-810c-e6f71650ab68) ​ ​ --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.qatts.com/administration/deployment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.