The dependence on properly functioning software is very high for many organisations. To prevent minor 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 goes hand in hand with (even) more administration. And that is exactly where the strength of Testersuite lies!
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.
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 convenient tree structure, in which the risk class is defined for each 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 transparent... from A to Z!
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 and preparation phase has been completed, in the specification phase test cases and test scenarios are drawn up in Testersuite (and not in Excel!) with a depth based on the risk class. By also planning the tests in the execution phase based on the risk classes, the biggest risks are covered first. Any defects from the test is recorded immediately and appears directly on the findings list for further processing.
A very valuable phase is the completion phase. Here it is determined, among other things, which test ware can be reused in the future. In Testersuite almost everything can be secured for future re-use, from risk classes to test scenarios. This makes it possible to keep the Preparation and Specification phases to a minimum during a new test. Besides limiting disruptions, Testersuite saves a considerable amount of time!
If you choose TMap Next to give structure and direction to the test approach, Testersuite offers a powerful tool to implement and secure this approach in a simple manner.
