TestBench Cloud Services was developed with a particular focus on agile teams and their functioning. The requirements of your products - the objects to be tested - are managed in the form of Epics and User Stories.
Describe the more significant 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 colors 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 into several sections. First, the preconditions can be marked as fulfilled. When you start the execution, you can set manually every test step from preparation to resetting the environment as passed or failed.
When a test step is set to failed, a 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 of a particular test step, can be created with the help of the "Global defects" field.