Author: Haroon Khalil
-
Static Test Tools
Static tests and analyses (such as reviews) can generally be performed on documents with any kind of structure, but tool-based static analysis relies on documents having as formal a structure as possible. For source code, the structure is prescribed by the syntax of the programming language, while formal specifications or models are governed by the…
-
Test Specification Tools
To ensure that a test case is reproducible, the individual testing steps, the test data, and the corresponding pre-and postconditions have to be defined and recorded. Most test management tools offer templates or familiar notations to support the creation of consistently structured test cases. These include keyword- or interaction-based notations, as well as the generally…
-
Test Management Tools
Test management Test management tools offer ways to register, catalog, and manage test cases and their priorities. They also enable you to monitor the status of test cases—in other words, you can record and evaluate whether, when, or how often a test has been performed and the results it delivered (pass/fail). They help test managers…
-
Types of Test Tools
Tool types We can differentiate between various types (or classes) of test tools depending on the phase of the testing process you are involved in and the type of task you want to automate. Types of test tools are also subdivided into specialized categories2 for use with specific platforms or fields of application (for example, performance…
-
Introduction
This chapter provides an overview of the various types of tools that can be used to support software testing activities. We look at what these tools are capable of, and how to select and introduce the ones that are best suited to your particular project. Test tools1 are used to support single or multiple software testing…
-
Configuration 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…
-
Evaluation and Reporting
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…
-
Defect Status Tracking
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…
-
Classifying Failures and Defects
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…
-
Creating a Defect Report
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,…