Manual Test Runs

Manual tests
Test suites, cases and runs
Creating test runs
Adding test cases manually
Importing test cases from lists
Editing cases
Marking test cases as done
Assigning tests to testers
Submitting results
Deleting test runs

Manual tests

Manual testing is a critical component of overall test strategy, especially in areas such as UX, usability, comfort, accessibility and exploratory testing. Manual testing is also important when a more nimble approach is required in specific situations.

Testers can add, edit and manage test cases all from within the Tesults web interface and submit results to any Tesults project target. You may want to have specific targets setup for manual test results.

Access manual test results submission from the side bar of the results page. Only team members assigned a moderator (level 2) role or above can upload manual test results, the manual button is not visible without this role assignment.

Test suites, cases and runs

A test case is an individual test. A test suite is a group of test cases. A test run is a single run of the test cases. To submit manual test results you need to create a new test run. The test run will consist of test cases belonging to one or more suites.

Creating test runs

Click the Create test run button to create a new test run. A test run can contain one or more test cases.

You can choose a temporary name for your test run. This can be useful to identify a test run again if you do not submit results in one sitting. You can come back to an in progress test run and select it to continue working on it.

Important Manual test runs are intended to be temporary. Manual test runs are deleted 30 days after being created. The expectation is that results will be submitted within 30 days. To store test cases for the long term, use test lists. Test runs are not for test case management, they are for submitting results only.

Adding test cases manually

Add test cases to your new test run. To add each case manually click the Add new case button.

When adding test cases manually you can specify the following test case properties:

PropertyRequiredDescription
name*Name of the test.
result*Result of the test. Must be one of: pass, fail, unknown. Set to 'pass' for a test that passed, 'fail' for a failure.
suiteSuite the test belongs to. This is a way to group tests.
descDescription of the test.
reasonReason for the test failure. Leave this empty or do not include it if the test passed.
paramsParameters of the test if it is a parameterized test.
filesFiles that belong to the test case, such as logs, screenshots, metrics and performance data.
_customAny number of custom fields. These can be anything you want.

Click the 'Save case' button to add the case to the run.

Importing test cases from lists

Another way to add test cases is to import cases from a test list. Test lists are saved lists of test cases. Test lists can save testers a lot of time. Read more about test lists.

Click the Import button to import test list cases to the selected test run.

Editing cases

Click a test case and click the Edit button to edit it. You can also remove a test case from the test run by selecting it and clicking the Delete button.

Marking test cases as done

When adding test cases you have the option to mark cases as done or not done. All imported cases from a test list are initially marked as not done. Test cases that are marked incomplete in this way are neutral4 to make it easier for testers to know which test cases have yet to be looked at.

Before submitting test results all cases must be marked as done. Testers can either mark each test case as done as they go along, or they can mark them all done using the Mark All Done button.

Assigning tests to testers

Assign test cases to testers in the team. This makes it easy to share workload and keep track of what each person is testing.

View test cases assigned to each tester by selecting a team member from the 'Show Assigned Cases To Team Member' dropdown list on the side menu. If an individual is selected, an 'Assign' button is displayed. Click it to select cases for assignment to the selected team member. After assignment is complete, be sure to click the green 'Save' button if you are happy with the selections you have made.

Individual test cases or entire test suites can be selected for assignment. The number of test cases assigned to each team member are displayed in the main panel within the manual test run page.

Submitting results

Once all test cases in the test run are marked done the results can be submitted. Click the Submit button to submit results.

Select the appropriate target to upload results to. If results are submitted to the wrong target the run can be deleted by a team member assigned a moderator (level 2) role or above. However before deleting a test run you may want to create a new test list with an import of the results for the results so that they can be re-submitted to an alternate target later. To avoid these problems just be sure to select the correct target when submitting.

After submission, results can be viewed in the results view the same way automated test results are viewed. Notifications will be delivered to team members that are setup to receive them.

Deleting test runs

Click the Delete button to delete a manual test run. Manual test runs are automatically deleted 30 days after creation. Use test lists for persistent storage.