1. Test Manager is too slow to execute tests and log results
The workaround here is to create small test runs by selecting small set of tests (30-40) at a time. If you select 100s of the active tests to execute, the test manager takes will take more time to load all those tests for execution and slows down.
2. No need to pass/fail every test step to log result for every test case
You can select the pass/fail/block option from the top right corner to log result for the entire test case, instead of marking each step with the result.
3. Create a bug during test execution
If a test fails, you can click on the bug icon on the tool bar to create a new bug instantly. The test case steps, logs are automatically added to the bug along. The test case is automatically linked to the bug as well.
4. Update existing bug during test execution
If a test fails, you can choose to update the existing bug with information about that test case. You can find the bug using a query and then attach the bug with the failing test case. Test steps, logs are automatically added to the bug along with linkage.
5. Super fast test result logging
If you want to log test results for a bulk of test cases, there is no bulk edit in the test runner. But instead you can start the test execution by logging a result of the first test case and then select the dropdown where you see the test title. From the dropdown, you can choose to pass/fail/block the test cases by single/double/triple clicks to the test result status. Once you are done with all, just click save and close and results for all tests are updated.
( 0 Votes )
