What should be a test?
A good example of a test is something a user would like to do, or achieve. A user story or user journey should probably map 1:1 to a test case.Test examples
- Log in with correct credentials
- Log in with incorrect credentials
- Create a new task
- Edit a task’s due date
Creating a test
Creating a new test in QA.tech is very simple. You can create a test in the platform by following a few simple steps.- Click the “Add Test Case” button

- Choose a Suggested Test or Create your own.


- Name: Give your test a descriptive name (e.g., “Create a new user with admin permissions”)
- Goal: Describe what the test should accomplish (e.g., “Create an admin user and sign in with the new user”)
- Expected Result (optional): Define what success looks like (e.g., “A new admin user appears on the users page”)
- Dependencies: Configure which tests this should wait for or resume from
- Configurations: Add any required configuration values needed for the test
- Advanced: Additional settings including agent selection (defaults to Latest)
- Review the generated test


- Activate the test
- Move the test to a Scenario group
How to format your test
Writing a good goal
The goal is the main objective of the test case. The agent will use this both to build the steps and to solve the task if things change in the steps. Focus on describing what the agent should do during the test, rather than what it should validate (use expected result for that).Good goal examples
- Search for ‘Chair’, navigate to a product and add it to the cart
- Invite a new member of the role Admin to the project
- Open the customer support chat and write a message
- Action-oriented: Start with verbs like “Create”, “Search”, “Navigate”, “Add”
- Specific: Include the exact details needed (e.g., product name, user role)
- Focused: Describe the actions to take, not the validation criteria
Writing a good expected result
The expected result defines what should be verified at the end of the test. It should clearly describe what the agent should see or experience when the test is completed successfully.Good expected result examples
- The page should contain a user avatar
- A success message should be displayed and the user should be redirected to the product list
- The user should have received an email with a link to reset their password
- Observable: Focus on things that can be verified visually or through system responses
- Specific: Include exact elements, messages, or states to check for
- Outcome-focused: Describe the end state, not the steps to get there