The dependence on properly working software is very high for many organizations. To prevent small changes from leading to major disruptions, more and more time is being spent on testing. It is therefore not surprising that a testing methodology such as TMap Next is being embraced. Unfortunately, the added value of testing according to TMap comes with (even) more administration. And there lies precisely the strength of Testersuite!
A powerful 'TMap tool'
TMap is a collection of best-practices for the testing process and has become the de facto standard since 1995. The most important two basic principles are the business-driven test management (BDTM) approach, and the principles for a structured test process.
Business driven test management
An important part of the preparation is the mapping of product risks. The object to be tested is subdivided into smaller 'products', and together with the client (the 'business') it is determined which parts will lead to major damage if they do not function properly. In combination with the probability of error, a risk class is assigned to the product. The depth and sequence of tests are done on the basis of these risk classes. So much for the theory...
In practice, it is a huge task to define the structure of products and associated risks, to coordinate them and share them with others. Subsequently, it is a daily task, especially with larger test cycles, to ensure that the biggest risks are actually the most extensively prepared and the first to be tested. In this way, the risk-based approach often fails.
Testersuite offers the possibility to set up a clear tree structure, in which the risk class is defined per product, possibly including a motivation. The test specification and execution is monitored by means of risk-based reports, after which the tests are planned, assigned and executed on the basis of risks. With Testersuite as a tool, Business driven test management becomes easy and insightful.... from A to Z!
Structured test process
By phasing the testing activities, important components such as test preparation and completion receive the attention they deserve at the right time. In this way the limited time window for test execution is optimally used. The TMap phasing looks like this:
After the planning phase and the preparation phase are completed, in the specification phase test cases and test scenarios are created in Testersuite (and not in Excel!) with a depth based on the risk class. By then scheduling the tests based on the risk classes in the execution phase as well, the biggest risks are covered first. Any defects from the test are recorded immediately and appear directly on the findings list for further handling.
A very valuable phase is the completion phase. Among other things, this determines which testware is reusable for the future. In Testersuite almost everything can be secured for future reuse, from risk classes to test scenarios. This makes it possible to minimize the Preparation and Specification phases in a new test. In addition to curbing disruptions, Testersuite thus delivers significant time savings!
If you choose TMap Next to give structure and direction to the testing approach, Testersuite provides a powerful tool to easily implement and secure this approach.
