Category: Test Management

A software system comprises a large number of individual components that have to work perfectly together if the complete system is to function properly. In the course of development, each of these components exists in new, corrected, or improved versions. For large projects, multiple development and testing teams work in parallel, making it difficult to…

Test and project management can evaluate the defect database to provide an overview of the current state of defect correction and the resulting product quality.36 Input for test and project management Test management uses evaluation results and defect-based metrics to adapt the test plan (for example, to add tests for particularly fault-prone components, or for…

Alongside effective defect management, the test manager also has to verify that any corrections made adequately remedy the faults that cause the recorded defects. This requires continuous end-to-end monitoring of the defect analysis and correction process, from discovery and registration to the finished solution. An issue can also be “solved” by accepting the limitations that…

The correction of defects is managed via the reports in the defect database. The urgency of correcting any particular fault depends on how seriously it affects the product’s users. There is a big difference between unsolved failures that cause system crashes and defects that document simple visual issues in the interface layout. Defects that significantly…

A development project will usually have a central defect database for recording and managing all issues, incidents, defects, or failures that are discovered in the course of testing and use of the product. As previously mentioned, defect reports can relate to any kind of issue in a system or its components, as well as errors,…

The result of every systematically performed test run is a test (execution) log23. This documents (per test case and/or testing step) the actual behavior observed during the test, the expected behavior, and any deviations between the two24. Analyzing test reports When analyzing a defect report25, you have to decide which of the deviations between expected…

If you want to correct defects reliably, you need a well-thought-out system for recording, communicating, and managing the defects, faults, and other issues that testing reveals. All the activities that this comprises make up the process known as defect management.22 Define the workflow for registering and processing incidents and defects A defect management process consists…

The objective of a test report is to summarize and communicate the current state of testing activity to the project manager and other stakeholders. This normally takes place routinely at the end of an iteration/test cycle or when a particular test activity (for example, performance testing) is completed. However, an interim test report can be…

Test cycle monitoring is all about collecting information and feedback relating to all test activities. Information can be collected manually or automatically and are then used to assess testing progress and evaluate whether the exit criteria or in agile projects the “definition of done” have been fulfilled. For example, these could be fulfillment of product…

Test control comprises all leadership, initiatory, and corrective measures that are performed in order to put into practice all test activities defined in the test plan and the test execution schedule. Controlling measures can directly affect testing activity or any other type of development activity. We differentiate between the following types of situations: React to…