TestBench Cloud Services was developed with a special focus on agile teams and their functioning. The requirements of your products - the objects to be tested - are managed in form of epics and user stories.
Describe the bigger features in epics and define the details from an end user's perspective in user stories. All objects and open activities within your product - from epics to user stories to test cases - are displayed on the product overview screen.
More information about the meaning of the symbols and colours can be found in the section "Review quality".
Specify all preconditions for your test cases, which are necessary for the execution.
Steps for preparation, for navigation, for performing the main test activities, for checking the result and for resetting the test object after the tests. With these test sequences you can verify the acceptance criteria of your user stories.
The test execution history shows all performed test executions. The status of the latest execution is the current status of the test case.
The test sequence is separated in several sections. First the preconditions can be marked as fulfilled. When you start the execution, every test step from preparation to resetting the environment can be manually set as passed or failed.
When a test step is set to failed, a defect form opens automatically to create a new defect to the test step. Report your bugs, classify them in terms of status, priority and severity and add users, which are responsible for the defect.
Defects, which are independent from a special test step, can be created with the help of the "Global defects" field.
An overview over the test progress and the reached quality is presented in all views. See open activities attached to the affected objects - directly and always up-to-date.
If any essential data is missing, an open activity is automatically created. TestBench Cloud Services shows the user not only the activities to be completed, but also their urgency and cumulates this information to the level of user stories and epics.
The object levels are displayed as follows:
Open activities are displayed with symbols, colours and numbers.
The open activities have three different urgencies:
blue note: activity was created less than seven days ago, low urgency
orange flash: activity was created less than 14 days ago, medium urgency
red flame: activity was created more than 14 days ago, high urgency
Each element also has its own progress statistics. This shows the user the progress of the test specification, but also the fulfillment of the test preconditions, such as the presence of the necessary test data. Here too, the information is displayed cumulatively on the upper levels.
On the picture you can see the progress of a user story: the left bar shows the degree of completness of the test specification of the linked test cases, the right bar shows the degree of the fulfilled preconditions of the linked test cases.
To ensure that the current statuses of the test results can be read at any time, the test case statuses are also displayed at all levels. Thus, the relationship between a found defect and the associated user story is always visible.
The status can be read directly from the test cases. Also, which test case is ready for test execution (status "Ready" with an open activity "Execute test case"). At the level of the associated user story, these status are then cumulated and visualized for all test cases of this user story:
In addition to the defects found and those that have not yet been corrected, the product quality assured by tests is also displayed. The product quality is calculated from the number of test cases run with "passed" in relation to the coverage of the user stories with linked test cases.