Creating Tests
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
At the top of the page you will find a button to create a new test.
- Choose a Detected Test or Create your own.
Our agents are continuously scanning your site for things to test. Things it finds will pop up as suggestions here in the detected tests list. You can either choose one or many of the suggestions or create your own using a freetext description.
Detected tests - Select a detected test from the list and click continue
Create your own test - Enter a freetext objective for the test
Make sure to choose which other test the new test should depend on.
- Review the generated test
Once the new test is generated and starts to create a test plan you are able to review the test.
To review the test, click the review button next to your new test.
This will take you to the edit test page.
At this stage the agent will attempt to achieve the objective on its own and generate steps for you. Once finished you will have a suggested test plan.
The sidebar to the left shows you the generated goal, expected result and suggested steps. In the Settings tab you have the possibillity to change dependencies, add configs the test needs or change advanced options for the agent.
To the right you have the trace of the attempted execution. Inspect that the agent correctly achieved what you want to test.
If you want to change anything in the plan you can update it and click “Save & Run” to see a new attempt with the updated test plan.
It is always possible to stop the agent by clicking the “Stop” button.
- Activate the test
Once you have a test plan to your liking click on the “Activate” button in the top right corner. This will enable the test and make it part of your test suite.
- Move the test to a Scenario group
Back on the “Test cases” page you can drag and drop the test to a Scenario group of your choosing. Grouping tests in Scenarios is a good way to keep your tests organized and helps get a good overview during execution.
How many steps should a test have?
Try to keep your test to 10 steps or less. If your test requires more steps, consider creating a new test with a chained dependency instead. Tests with too many steps have the downside of taking longer to execute, and being harder to maintain.