> For the complete documentation index, see [llms.txt](https://docs.optibase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optibase.io/features/tests/auto-stop-a-test.md). # Auto Stop a Test {% embed url="" %} Optibase lets you automatically stop a test when certain criteria are met. This ensures you don’t keep running tests longer than needed, saving time and traffic.
*** ### How to enable Auto Stop 1. Open your test in the Optibase Web App 2. Click the Auto stop button in the test header 3. Enable one or more conditions from the list 4. Set the values for each condition 5. Close the panel — your settings are saved automatically *** ### Available auto-stop conditions You can stop a test when any of the following conditions are true: * When conversions equals Stop the test when total conversions across all variants reach a specific number *Example: Stop at 1000 conversions* * When conversion rate is Stop the test when a variant reaches a specific conversion rate *Example: Stop if a variant hits 5%* * When tested users reach Stop the test when a specific number of unique tested users have seen the variants *Example: Stop after 1000 tested users* * When P2BB is Stop the test when a variant reaches a given Probability to Be Best (P2BB) *Example: Stop if a variant hits 95% P2BB* > You can use any combination of these rules — the test will stop as soon as one is satisfied. *** ### What happens when a test auto-stops? * The test status changes to Paused * No more traffic is distributed to variants * The best-performing variant (based on current results) is shown to all users * You can still view historical results and restart the test if needed --- # 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.optibase.io/features/tests/auto-stop-a-test.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.