Test Execution is an entity which groups together the test cases and their testers. They can be easily assigned and monitored.
Before executing the assigned tests a tester goes through a pre-execution screen,
On this screen user will be shown summary of test(s) to be executed, which covers
Number of Test suites under the defined Test Execution
Number of test cases to be covered during the execution
Estimated execution time which depends on the previous executions for same tests
Name of the project member who has defined the Test Execution.
An option to either start or resume the execution depending upon the status of the previous executions will be available.
As parameter the priority and any other custom parameters (fields and their values) set for this Test Execution.
List of related test suites (the test cases belonging to which have to be executed)
For individual test suite covered in Test Execution, the details of cases under it covering individually test case name, and estimated execution time, will be shown on clicking the suite's title.
Running the Tests
After pre-execution screen on selection of either Start Now, or Resume option, test run screen is displayed.
If sequential execution / popup-window for execution is enabled then while user is executing/running the tests, a separate window to manage the running tests and provide his feedback on individual test case back to the Test Collab application, would be shown.
Since this screen is shown on a separate small window it will not hinder the execution process for the test.
If sequential execution / popup-window for execution is disabled then the same window will be used to let the tester provide his feedback. This provides an option for tester to move back and forth between the executable test cases by directly selecting the same from suites tree.
On the window the user can see
The progress of the entire test so far
The time so far spent during execution of a particular test case
Estimated time, if the test case has earlier been executed
User has the option to stop / resume the time logging for execution of this test case.
Followed by these will be details of the test case being executed, including
The test suite name
Test case title
Steps to be followed, sequentially arranged in the order in which they are to be executed
Expected results for the test case, once all the steps are performed
For user to provide his feedback he has options to
Leave his comment
Upload one or more file to attach with the execution record of the particular test case, the files thus attached, would also be linked with the issue at the time of reporting, in case of failure
Most importantly the user will be required to set the result of this test case; user can
Mark the test as passed, or
Mark the test as failed, or
Mark the test as failed and report the same through issue manager (if an issue manager has been associated with application and if the project specific settings have been defined for issue manager), or
He can simply skip the test
Executions when separate text fields for steps and their expected results have been enabled for project.
If while creating the project you have enabled separate text fields for steps and expected results then the execution window will allow you to mark each step as passed / failed / skipped moreover tester can also leave comments for each step individually.
If email notification for action(s) performed here has been enabled by administrator, then the same would be sent.