-
Notifications
You must be signed in to change notification settings - Fork 31
Execution
From the list of testcases - weather it is a grouped list or a testsuite - a user can create a TestRun.
This is what allows users to execute testcases during software test cycle. TestRun is a copy of testcases selected for execution. Testcases in TestRun won't change if original testcases will be changed.
There are 4 states that could be assigned to a testcase in TestRun: PASSED - actual results meet expectations FAILED - actual result don't match expectations BROKEN - testcase is broken and needs to be fixed or updated SKIPPED - testcase is being skipped within TestRun for some reason
TestRuns are stored permanently. The data could be used as execution reports for many purposes. TestRuns could be filtered (in development) and statistical information could be build according to the filter. This will allow to analyze testruns, find bottlenecks and issues in a software testing life cycle.
TestRuns also contain statistical data about themselves - participants, execution time, e.t.c. That data is available through UI as well as API.
Test runs could be updated from "outside" using REST-API. This allows to run executions outside - e.g. - automated testcases. Test External Runner Systems should be able to return back results using API.