A test run in TestMonitor is the actual test you are conducting. Test runs allow you to assign test cases to one or more testers. You might use them to indicate the release of certain deliverables, the completion of a sprint or a specific testing objective.
In most projects it is likely that you plan multiple test runs for a set of test cases and users over time. If you want to execute particular test cases for multiple configurations (such as different operating systems) planning multiple test runs makes sense.
In TestMonitor you can organize your test runs into milestones. Milestones signify important project events. These can be the release of a beta version or the completion of a user acceptance test.
It is advised to name your milestones based on releases or sprints, for example: TestMonitor 5.1 release or Sprint 2.
Add a Milestone
Before adding test runs you must first specify a Milestone. You can find the milestones overview by clicking Plan in the header. You can see all the milestones that are assigned to your currently selected project. In this overview you can add, edit and delete your milestones.
To add a milestone, simply click the Add milestone… button. Fill in the mandatory name and optional description. You will also have to fill the date of the milestone. This date marks the enddate of the milestone. Choose Save to create your first milestone.
Add a Test Run
After creating a milestone, the next step is to plan a test run. Test runs are part of a milestone and are used to assign test cases to users.
You can plan a test run by selecting the milestone name or use the arrow button at the right of the milestone to go to the milestone details.
Next, you can click the Add Test Run... button in the top right. A pop up appears allowing you to create your test run.
To specify a new test run you need to fill the following fields:
- Specify general properties
The first step in planning a test run is giving your testrun a name. Once you've done that, you can set the start and end date for the test run.The start date and end date of your test run define the time period in which a test run will be available to your testers. Before and after these dates they will not be able to execute the test run. Last but not least, you can set your test run to priority when necessary.
- Assign test cases
Next, you can assign test case(s) to a test run. In the pop up you can find a list of all test cases in the project. The filter icon left at the top of the test cases list allows you to open the filters bar. You can use filters to find specific test cases matching your search parameters. There are five filters available, Test Suite, Requirements, Risks, Applications and Tags. Use the cog button at the right of the test cases list to add or remove filters. The search field next to the filter icon allows you to find a test case matching your search parameters. Select the + for the test cases you want your testers to test in this test run.
- Assign users
Last step is to assign user(s) to your test run. In the pop up you will find a list of all your users authorised for the project that is currently selected. Select the + for the users that you want to assign to this test run.
Users assigned to a test run will optionally receive a reminder by e-mail when their run becomes available for testing. You can turn notification on/off in your user settings.
Once you have successfully created your test run, assigned users will be able to access the test run in the time period you've set for the test run.
You can update properties, assigned test cases, and assigned users for your test run after the test run has been created. Go to the test run details page by either selecting the line of the test run or the 'arrow' button to the right of the test run.