Please enable JavaScript.
Coggle requires JavaScript to display documents.
Test Design Techniques : - Coggle Diagram
Test Design Techniques :
4.3 Specification-based or black-box techniques
4.3 - Specification-based (black-box) testing techniques
4.3.2 Decision table testing ('cause-effect' table)
Creating a table listing all the combinations of True and False for each of the aspects
Combinations of things (e.g. inputs, conditions, etc.)
4.3.3 State transition testing ('finite state machine')
Model can be as detailed or as abstract as you need it to be
Four basic parts:
The states that the software may occupy (open/closed or funded/insufficient funds)
The events that cause a transition (closing a file or withdrawing money)
The transitions from one state to another (not all transitions are allowed)
The actions that result from a transition (an error message or being given your cash)
4.3.1 Equivalence partitioning and boundary value analysis
Boundary value analysis (BVA) is based on testing at the boundaries between partitions
EP are also known as equivalence class
Designing test cases
both EP and boundary value analysis
Invalid inputs are separate test cases
4.3.4 Use case testing
Is a technique that helps us identify test cases that exercise the whole system on a transaction by transaction basis from start to finish
4.2 Categories Of Test Design Techniques
Introduction
Dynamic
Structure-Based (White Box)
Condition
Decision
Multiple Condition
Statement
Speccification Based (Black Box)
State transition
Decision Table
Usecase Testing
Boundary Values
Static
Techniques Review
Inspection
Walkthough
Informal Review
Static testing techniques
Non-execution techniques
Static Analyses
Specification-based (Black-Box) techniques
'Black box' testing techiques or in/out put techniques
Funtional
Non-Funtional
Include performance, usability,...
Dynamic testing techniques
Structure-based(White-box) testing techniques
Dynamic
'White-Box' or 'Glass-Box' techniques
4.1 - IDENTIFYING TEST CONDITION AND DESIGNING TEST CASES
4.1.1 - The glossary terms
test data
test procedure specification
test condition
test script
test specification
traceability
test case
4.1.2 - The Folmality of test documentation
informal testing
formal testing
4.1.3 - The analysis
test possibilities
identify as many as we can
start being selective about which ones to take forward to dev in more detail
combine into test cases
testing technique
select a good set of tests from the total number of all possible tests for a given system
Different techniques offer different ways of looking at the software under test
test basic
based on an experienced user's knowledge of the system
include whatever the tests are based on
be a system requerement, a technical specification, the code itseft, or a business process
4.1.4 - Test design: specifying test cases
expected results
what if we dont decide on the expected results before we run a test?
test case assesses that the system does what it is suppose to do
4.1.5 - Test implementation specifying test procedures or scripts
group the test cases
test schedule
The logical and technical dependencies between the scripts
writing the test procedure
4.4 STRUCTURE-BASED OR WHITE-BOX
TECHNIQUES
4.4.1 Using structure-based techniques to measure coverage and design tests
Structure-based test design techniques text
How to measure coverage
Inserting instrumentation
Decide on the structural element to be used, i.e. the coverage
Count the structural elements or items
Instrument the code
Run the tests for which coverage measurement is required
Using the output from the instrumentation, determine the percentage of ele
ments or items exercised.
Requires tool support (For mos pratical purposes)
Types of coverage
Coverage can be measured at componenttesting level, integration-testing level or at system- or acceptance-testing levels
We can measure coverage for each of the specification-based techniques as
well
: percentage of equivalence partitions exercised
percentage of boundaries exercised
Decision tables: percentage of business rules or decision table columns
tested
State transition testing: there are a number of possible coverage measures
Generating additional test cases that are different from existing tests
Serve two purposes: test coverage measurement and structural test case design
Help ensure more breadth of testing
What is test coverage?
4.5 - Experience-based techniques
4.5.1 - Error guessing
A structure approach to the error-guessing technique is to list possible defects or failures and to design tests that attempt to produce them
can be built based on
experience of other people
available defect and failure date
from common knowledge about why software fails
the tester's own experience
4.5.2 - Exploratory testing
is a hands-on approach in which testers are involved in minimum planning and maximum test execution
A key aspect of exploratory testing is learning