Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component
It attempts to find:
Incorrect or missing functions
Interface errors
Errors in data structures or external database access
Performance errors
Initialization and termination errors
Black-box test design treats the system as a "black-box", so it does not explicitly use knowledge
of the internal structure. Black box testing is based solely on the knowledge of the system requirements. Black-box test design is usually described as focusing on testing functional requirements.
In comparison, White-box testing allows one to peek inside the "box", and it focuses specifically on using internal knowledge of the software to guide the selection of test data .
Black box testing focuses on testing the function of the program or application against its specifications. Specifically, this technique determines whether combinations of inputs and
operations produce expected results.
Test Case design Techniques under Black Box Testing:
Equivalence class partitioning
Boundary value analysis
Comparison testing
Orthogonal array testing
Decision Table based testing
Cause Effect Graph
Determination of equivalence classes
Examine the input data.
Few general guidelines for determining the equivalence classes can be given
If the input data to the program is specified by a range of values:
e.g. numbers between 1 to 5000.
One valid and two invalid equivalence classes are defined.
If input is an enumerated set of values:
e.g. {a,b,c}
one equivalence class for valid input values
Another equivalence class for invalid input values should be defined.
Example
A program reads an input value in the range of 1 and 5000:
computes the square root of the input number
There are three equivalence classes:
the set of negative integers,
set of integers in the range of 1 and 5000,
Integers larger than 5000.
The test suite must include:
representatives from each of the three equivalence classes:
A possible test suite can be: {-5, 500, 6000}.
ERROR CHECK LIST FOR INSPECTIONS
WALK THROUGHS IN TESTING
TESTING FOR SPECIALIZED ENVIRONMENTS PART ONE
TESTING FOR SPECIALIZED ENVIRONMENTS PART TWO
VALIDATION TESTING
SYSTEM TESTING
DEBUGGING AND TESTING
DEFECT AMPLIFICATION AND REMOVAL
ITERATIVE SPIRAL MODEL
STANDARD WATER MODEL
CONFIGURATION MANAGEMENT
CONTROLLED TESTING ENVIRONMENT
RISK ANALYSIS PART ONE
RISK ANALYSIS PART TWO
BACK GROUND ISSUES
SOFTWARE REVIEWS PART ONE
SOFTWARE REVIEWS PART TWO
SOFTWARE RELIABILITY
SAFETY ASPECTS
MISTAKE PROOFING
SCRIPT ENVIRONMENT
V MODEL IN TESTING
It attempts to find:
Incorrect or missing functions
Interface errors
Errors in data structures or external database access
Performance errors
Initialization and termination errors
Black-box test design treats the system as a "black-box", so it does not explicitly use knowledge
of the internal structure. Black box testing is based solely on the knowledge of the system requirements. Black-box test design is usually described as focusing on testing functional requirements.
In comparison, White-box testing allows one to peek inside the "box", and it focuses specifically on using internal knowledge of the software to guide the selection of test data .
Black box testing focuses on testing the function of the program or application against its specifications. Specifically, this technique determines whether combinations of inputs and
operations produce expected results.
Test Case design Techniques under Black Box Testing:
Equivalence class partitioning
Boundary value analysis
Comparison testing
Orthogonal array testing
Decision Table based testing
Cause Effect Graph
Determination of equivalence classes
Examine the input data.
Few general guidelines for determining the equivalence classes can be given
If the input data to the program is specified by a range of values:
e.g. numbers between 1 to 5000.
One valid and two invalid equivalence classes are defined.
If input is an enumerated set of values:
e.g. {a,b,c}
one equivalence class for valid input values
Another equivalence class for invalid input values should be defined.
Example
A program reads an input value in the range of 1 and 5000:
computes the square root of the input number
There are three equivalence classes:
the set of negative integers,
set of integers in the range of 1 and 5000,
Integers larger than 5000.
The test suite must include:
representatives from each of the three equivalence classes:
A possible test suite can be: {-5, 500, 6000}.
ERROR CHECK LIST FOR INSPECTIONS
WALK THROUGHS IN TESTING
TESTING FOR SPECIALIZED ENVIRONMENTS PART ONE
TESTING FOR SPECIALIZED ENVIRONMENTS PART TWO
VALIDATION TESTING
SYSTEM TESTING
DEBUGGING AND TESTING
DEFECT AMPLIFICATION AND REMOVAL
ITERATIVE SPIRAL MODEL
STANDARD WATER MODEL
CONFIGURATION MANAGEMENT
CONTROLLED TESTING ENVIRONMENT
RISK ANALYSIS PART ONE
RISK ANALYSIS PART TWO
BACK GROUND ISSUES
SOFTWARE REVIEWS PART ONE
SOFTWARE REVIEWS PART TWO
SOFTWARE RELIABILITY
SAFETY ASPECTS
MISTAKE PROOFING
SCRIPT ENVIRONMENT
V MODEL IN TESTING
No comments:
Post a Comment