OnTest
| Software Testing & Quality Engineering |
 | |  | |  | |  | |  |
Testing Techniques
There are a large number of techniques that are used today to test software products. In most cases, only a subset
of these techniques are applicable and are actually used. A 'Divide and Conquer' strategy always pays off when testing
large/complex systems. The approach allow us to divided the systems into smaller testable components first and then
select the appropriate techniques(s) to thoroughly test it. Here is a list of most common testing techniques:
Black-box Testing
Not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
White-box Testing
Based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements,
branches, paths, conditions.
Unit Testing
The most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and
not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done
unless the application has a well-designed architecture with tight code; may require developing test driver modules
or test harnesses.
Incremental Integration Testing
Continuous testing of an application as new functionality is added; requires that various aspects of an application's
functionality be independent enough to work separately before all parts of the program are completed, or that test
drivers be developed as needed; done by programmers or by testers.
Integration Testing
Testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code
modules, individual applications, client and server applications on a network, etc. This type of testing is especially
relevant to client/server and distributed systems.
Functional Testing
Black-box type testing geared to functional requirements of an application; this type of testing should be done by
testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which
of course applies to any stage of testing.)
System Testing
Black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.
End-to-End Testing
Similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in
a situation that mimics real-world use, such as interacting with a database, using network communications, or
interacting with other hardware, applications, or systems if appropriate.
Sanity Testing or Smoke Testing
Typically an initial testing effort to determine if a new software version is performing well enough to accept it for a
major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems
to a crawl, or corrupting databases, the software may not be in a 'sane' enough condition to warrant further testing
in its current state.
Regression Testing
Re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much
re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially
useful for this type of testing.
Acceptance Testing
Final testing based on specifications of the end-user or customer, or based on use by end-users/customers over
some limited period of time.
Load Testing
Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the
system's response time degrades or fails.
Stress Testing
Term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system
functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large
numerical values, large complex queries to a database system, etc.
Performance Testing -
Term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of
testing) is defined in requirements documentation or QA or Test Plans.
Usability Testing
Testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User
interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers
are usually not appropriate as usability testers.
Install/Uninstall Testing
Testing of full, partial, or upgrade install/uninstall processes.
Recovery (Fault Tolerance) Testing
Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
Failover Testing
Typically used interchangeably with 'recovery testing'.
Security Testing -
Testing how well the system protects against unauthorized internal or external access, willful damage, etc; may
require sophisticated testing techniques.
Compatibility Testing
Testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
Exploratory Testing
Often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may
be learning the software as they test it.
Ad-hoc Testing
Similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software
before testing it.
Context-driven Testing
Testing driven by an understanding of the environment, culture, and intended use of software. For example, the testing
approach for life-critical medical equipment software would be completely different than that for a low-cost computer
game.
User Acceptance Testing
Determining if software is satisfactory to an end-user or customer.
Comparison Testing
Comparing software weaknesses and strengths to competing products.
Alpha Testing
Testing of an application when development is nearing completion; minor design changes may still be made as a
result of such testing. Typically done by end-users or others, not by programmers or testers.
Beta Testing
Testing when development and testing are essentially completed and final bugs and problems need to be found
before final release. Typically done by end-users or others, not by programmers or testers.
Mutation Testing
A method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes
('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation
requires large computational resources.
Data Modeling
Brings to light the relationships that may be missing from the requirements; tells testers which relationships they need
to test.
Decision Tables
Describe in a precise manner how a software system behaves; supplements exit criteria; scenario based.
State Modeling
Diagrams with boxes and lines between them; the diagram outlines all the possible scenarios that need to be tested;
every path on the diagram represents a scenario.
Equivalence Class Partitioning
Applies to 100% of requirements; helps determine valid and invalid input and the software system’s reaction to those
values; help determine the number of test cases needed.
Impact Analysis
Supplements regression testing; analysis of impact of new (or modified) code on the rest of the system.
Certification Testing
Used to certify the software system for a particular use or environment.
Localization/Internationalization Testing
Testing for support of different languages and locales.
< Back to previous page
There are a large number of techniques that are used today to test software products. In most cases, only a subset
of these techniques are applicable and are actually used. A 'Divide and Conquer' strategy always pays off when testing
large/complex systems. The approach allow us to divided the systems into smaller testable components first and then
select the appropriate techniques(s) to thoroughly test it. Here is a list of most common testing techniques:
Black-box Testing
Not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
White-box Testing
Based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements,
branches, paths, conditions.
Unit Testing
The most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and
not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done
unless the application has a well-designed architecture with tight code; may require developing test driver modules
or test harnesses.
Incremental Integration Testing
Continuous testing of an application as new functionality is added; requires that various aspects of an application's
functionality be independent enough to work separately before all parts of the program are completed, or that test
drivers be developed as needed; done by programmers or by testers.
Integration Testing
Testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code
modules, individual applications, client and server applications on a network, etc. This type of testing is especially
relevant to client/server and distributed systems.
Functional Testing
Black-box type testing geared to functional requirements of an application; this type of testing should be done by
testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which
of course applies to any stage of testing.)
System Testing
Black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.
End-to-End Testing
Similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in
a situation that mimics real-world use, such as interacting with a database, using network communications, or
interacting with other hardware, applications, or systems if appropriate.
Sanity Testing or Smoke Testing
Typically an initial testing effort to determine if a new software version is performing well enough to accept it for a
major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems
to a crawl, or corrupting databases, the software may not be in a 'sane' enough condition to warrant further testing
in its current state.
Regression Testing
Re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much
re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially
useful for this type of testing.
Acceptance Testing
Final testing based on specifications of the end-user or customer, or based on use by end-users/customers over
some limited period of time.
Load Testing
Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the
system's response time degrades or fails.
Stress Testing
Term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system
functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large
numerical values, large complex queries to a database system, etc.
Performance Testing -
Term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of
testing) is defined in requirements documentation or QA or Test Plans.
Usability Testing
Testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User
interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers
are usually not appropriate as usability testers.
Install/Uninstall Testing
Testing of full, partial, or upgrade install/uninstall processes.
Recovery (Fault Tolerance) Testing
Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
Failover Testing
Typically used interchangeably with 'recovery testing'.
Security Testing -
Testing how well the system protects against unauthorized internal or external access, willful damage, etc; may
require sophisticated testing techniques.
Compatibility Testing
Testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
Exploratory Testing
Often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may
be learning the software as they test it.
Ad-hoc Testing
Similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software
before testing it.
Context-driven Testing
Testing driven by an understanding of the environment, culture, and intended use of software. For example, the testing
approach for life-critical medical equipment software would be completely different than that for a low-cost computer
game.
User Acceptance Testing
Determining if software is satisfactory to an end-user or customer.
Comparison Testing
Comparing software weaknesses and strengths to competing products.
Alpha Testing
Testing of an application when development is nearing completion; minor design changes may still be made as a
result of such testing. Typically done by end-users or others, not by programmers or testers.
Beta Testing
Testing when development and testing are essentially completed and final bugs and problems need to be found
before final release. Typically done by end-users or others, not by programmers or testers.
Mutation Testing
A method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes
('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation
requires large computational resources.
Data Modeling
Brings to light the relationships that may be missing from the requirements; tells testers which relationships they need
to test.
Decision Tables
Describe in a precise manner how a software system behaves; supplements exit criteria; scenario based.
State Modeling
Diagrams with boxes and lines between them; the diagram outlines all the possible scenarios that need to be tested;
every path on the diagram represents a scenario.
Equivalence Class Partitioning
Applies to 100% of requirements; helps determine valid and invalid input and the software system’s reaction to those
values; help determine the number of test cases needed.
Impact Analysis
Supplements regression testing; analysis of impact of new (or modified) code on the rest of the system.
Certification Testing
Used to certify the software system for a particular use or environment.
Localization/Internationalization Testing
Testing for support of different languages and locales.
< Back to previous page
| © 2007 Raassi & Associates, Inc. All rights reserved |