Author: Haroon Khalil
-
Testing and Risk
“Risk” is one of the best criteria to use when selecting and prioritizing test objectives, testing techniques, and test cases. Risk = (expected loss in case of accident) x (the probability of the accident occurring) Risk is defined as the product of the expected loss in the case of an accident and the probability of…
-
Concrete Strategies
In practice, testing strategies are built up using a mixture of the various approaches described above. For example, you can combine risk-based testing (an analytical approach) with exploratory testing (a reactive strategy element). The following variants are often used in real-world situations:
-
Selecting a Testing Strategy
Selecting an overall testing strategy is one of the most important decisions that a test manger has to make. The overall objective is to establish a set of measures that maximize the effectiveness and efficiency of testing within the predefined project constraints. Or, viewed the other way around, the overall objective of testing is to…
-
Testing Strategies
Test Planning A task as complex as testing requires meticulous planning on an operational level and on a strategic level. The starting points for strategic planning are provided by company testing policy and testing guidelines (if they exist), or by a generic company testing strategy. The test manager needs to transpose such generic guidelines to…
-
Roles, Tasks, and Qualifications
In order to perform the testing process efficiently and professionally, a project requires staff with knowledge and experience in all aspects of the multi-facetted testing oeuvre. The following roles need to be filled, ideally with appropriately qualified personnel. Test manager The test manager takes responsibility for all test activities in one or more development projects,…
-
Test Organization
Independent Testing A software product has to be tested throughout its lifecycle so testing activities have to be well coordinated with all other development activities. The simplest and most obvious solution is to have the developers do their own testing. However, this approach typically leads to developers being “blind to their own mistakes”, so it…
-
Introduction
How to organize test teams, which skills are important, a test manager’s role, and which supporting processes help to make testing more efficient.
-
Evaluation of Black-Box Testing
Faulty specifications or requirements are not revealed All black-box testing techniques are based on the requirements and/or specifications of a system or its components and their interactions. If the requirements include erroneous definitions or an erroneous specification was used as the basis for an implementation, black-box testing will not reveal these defects. This is because…
-
Use-Case Testing
Use cases and business cases are often used to determine and document system requirements. These are generally illustrated using use case diagrams. Such diagrams describe typical use/system interactions and are used to specify requirements on a fairly abstract level. Figure 5-8 shows a use case diagram for part of the VSR-II vehicle selection process. Example Fig. 5-8Use-Case diagram for…
-
Testing Tools
Open-source tools You are sure to be asking yourself which formulae you can use to derive your n-wise test cases. Fortunately, there are plenty of dedicated software tools available that do (most of) the work for you. We are not in the business of advertising, but the authors of the German-language OpenBook “Lean Testing for…