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.
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.
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 such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate....
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.
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.
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.
0 comments:
Post a Comment