> ## Documentation Index > Fetch the complete documentation index at: https://docs.docketqa.com/llms.txt > Use this file to discover all available pages before exploring further. # Test Suites > Test suites are a grouping of tests on Docket ### Test Suite Test suites are collections of tests on Docket. They are used to organize tests into logical groups that you might want to run together. > **Next Step**: After creating a test suite, you can [create individual tests](/essentials/test-creation) to add to the suite. ### Creating a test suite To create a test suite, navigate to the test suites tab. Screenshot 2025-07-17 at 3.52.48 PM.png From there, click the "New Test Suite" button and give your test suite a suitable name. Screenshot 2025-07-27 at 4.03.55 PM.png ### Accounts Think of accounts as username and password configurations that Docket uses to log in. You can assign accounts to test suites, which will then use that account to authenticate for all tests in the suite. Docket will navigate to the provided URL and log in with the credentials. The browser state (cookies, local storage) that results from this login will be copied as the starting point for all other test runs. Screenshot 2025-07-17 at 3.59.28 PM.png You can then assign this account as the login module for any test suite: Screenshot 2025-07-17 at 3.59.56 PM.png ### Region Select the geographical region where your tests will execute. Choose a region close to your servers for best performance and lower network latency. ### Notifications Configure email, Slack, or webhook [notifications](/essentials/notifications) for test results. ### Variables Define key-value pairs at the suite level and reference them in test steps using `@variable_name` syntax. Mark random or email variables as **fixed** to share the same generated value across all tests in a suite run. ### Agent Rules Add suite-level [agent rules](/essentials/agent-context) that apply to all tests in the suite. These are combined with your company-wide rules. ### Scheduling a Test Suite You can also schedule all tests in a given test suite to run at regular intervals. See the [scheduling section](/essentials/running-test#scheduling-a-run) in the Running a Test guide for instructions on how to set this up. **Related Pages:** * [Creating a Test](/essentials/test-creation) - Learn how to add tests to your suite * [Running a Test](/essentials/running-test) - Different ways to execute your tests