Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 4: Test Design techniques - Coggle Diagram
CHAPTER 4: Test Design techniques
4.1 Identifying test conditions and designing test case
4.1.1 Formality of test documentation
The degree of test formality depends on: The type of application under test; Standards followed by your organization; The maturity of the development process
Type of test documents are: Test policy; Test strategy; Test plan; Test case
4.1.2 Test analysis: identifying test conditions
Test analysis is describes ”what” should be tested.
test basis
test condition
test possibilities
test techniques
The test conditions that are chosen will depend on the test strategy or detailed test approach.
Test conditions should be able to be linked back to their sources in the test basis - this is called traceability.
4.1.3 Test design: specifying test cases
Basically test design is the act of creating and writing test suites for testing a software.
A test case is a document, which has a set of test data, preconditions, expected results and postconditions
4.1.4 Test implementation: specifying test procedures or scripts
The document that describes the steps to be taken in running a set of tests and specifies the executable order of the tests is called a test procedure
Test implementation is an action when Procedure Specification is prepared and is implemented.
4.2 CATEGORIES OF TEST DESIGN TECHNIQUES
4.2.1 Static testing techniques
There are many different types of software testing technique, each with its own strengths and weaknesses
Each individual technique is good at finding particular types of defect and relatively poor at finding other types.
4.2.2 Specification-based (black-box) testing techniques
The first of the dynamic testing techniques we will look at are the specification based testing techniques.
4.2.3 Structure-based (white-box) testing techniques
Structure-based testing techniques (which are also dynamic rather than static) use the internal structure of the software to derive test cases
4.2.4 Experience-based testing techniques
n experience-based techniques, people's knowledge, skills and background are a prime contributor to the test conditions and test cases.
4.2.5 Where to apply the different categories of techniques?
Specification-based techniques are appropriate at all levels of testing (component testing through to acceptance testing) where a specification exists
When performing system or acceptance testing, the requirements specification or functional specification may form the basis of the tests.
4.3 SPECIFICATION-BASED OR BLACK-BOX TECHNIQUES
4.3.1 Equivalence partitioning and boundary value analysis
Equivalence partitioning:The idea behind the technique is to divide (i.e. to partition) a set of test conditions into groups or sets that can be considered the same (i.e. the system should handle them equivalently), hence 'equivalence partitioning'
Boundary value analysis (BVA) is based on testing at the boundaries between partitions.
4.3.2 Decision table testing
They provide a clear method to verify testing of all pertinent combinations to ensure that all possible conditions, relationships, and constraints are handled by the software under test.
4.3.3 State transition testing
State transition testing is used where some aspect of the system can be described in what is called a 'finite state machine'
4.3.4 Use case testing
A use case is a description of a particular use of the system by an actor (a user of the system).
Each use case describes the interactions the actor has with the system in order to achieve a specific task (or, at least, produce something of value to the user)
4.4 STRUCTURE-BASED OR WHITE-BOX TECHNIQUES
4.4.1 USING STRUCTURE-BASED TECHNIQUES TO MEASURE COVERAGE AND DESIGN TESTS
Structure-based techniques serve two purposes: test coverage measurement and structural test case design.
Structure-based test design techniques are a good way of generating additional test cases that are different from existing tests.
4.4.2 STATEMENT COVERAGE AND STATEMENT TESTING
A statement may be on a single line, or it may be spread over several lines.
.
Different tools and methods may count different things as statements, but the basic principle is the same however they are counted.
Some statements can contain other statements inside them.
4.4.3 DECISION COVERAGE AND DECISION TESTING
Decision coverage = (outcomes exercised/total decision outcomes)*100%
4.4.4 OTHER STRUCTURE-BASED TECHNIQUES
brand coverage