The imbus TestBench contains an interface for the import of requirements from external requirement management systems. If a requirement integration is installed for imbus TestBench, all user can read the requirements of their projects and easily link them with their tests, without the need for any additional software. To draw up, amend, and administer the requirements, you continue to use your usual requirement tool.
Requirements-based testing in few steps:
Step 1: For the requirements-based test, you first import a requirement baseline that contains all the requirements relevant to the test, for example in a tree structure. In the imbus TestBench, you can not only access the requirement texts, but also you have access to further fields, such as “status” or “priority” – in short: access to all the information that you need for planning and designing tests.
Step 2: Test managers or test designers then link requirements with – in some cases newly created – test themes or test case sets. In this way, the structure for the testing of requirements is drawn up and finally determined, which tests validate which requirements. Requirements that have not yet been assigned are optically highlighted so that it is possible to check at a glance whether all requirements have been covered by tests.
Step 3: In the following step, test designers specify particular tests within the given structure. At the same time, test managers can easily get an overview on all requirements for which tests are still missing.
As soon as the first tests have been executed, you can, at any time, check at a glance the test status of all requirements, or you can have this information issued in the form of a requirement report.
If requirements change in the course of the project (for example, for a release with extended functionality), you simply import the new requirements baseline. With a filter, you quickly find all the tests that might be affected by the change. And the best part is: If you have specified the tests in accordance with the interaction method, you only have to change one single test element for each amended detail of a requirement. All tests that use this test element are adapted automatically
For requirements-based tests, the tests are not only linked to the requirements, but also to the defects found during the test. That way, imbus TestBench can match requirements with defects and provide you with information about which requirements are being blocked by which defects. On the basis of this information, you can direct your development team in such a way that, for defect correction, they concentrate on the really critical requirements.