Testing Glossary

• Black-box testing - testing that verifies that given input A the component or system being tested gives you expected results B.
• Boundary-value testing - testing of unusual or extreme situations that your code should be able to handle.
• Function testing - a part of system testing in which development staff confirm that their application meets the specified user requirements.
• Integration testing - testing that verifies that several portions of software work together.
• Regression testing - testing that ensures previously tested behaviors still work as expected after changes have been made to an application.
• Stress testing - testing that ensures the system performs as expected under a high volume of transactions, high number of users, and so on. Also referred to as load testing.
• White-box testing - testing that verifies specific line of code work as defined. Also referred to as clear-box testing.
• Alpha testing - a testing period in which pre-release versions of software products are released to users who need access to the product before it it officially deployed. In return, these users will report any defects to the software developers. Alpha testing is typically followed by beta testing.
• Beta testing - a similar process to alpha testing, except the software product should be less buggy.
• Code inspection - a form of technical review in which the deliverable being reviewed is source code.
• Peer view - a style of technical review in which a project artifact, or portion thereof, is inspected by a small group of experts.
• Use-case scenario testing - a testing process in which users work through use cases with the aid of a facilitator to verify that a user interface prototype fulfills the needs of its users and that the identified classes for a system fulfill the requirements described in the use cases.
• User testing - testing processes in which the user community, as opposed to developers, performs the tests.
• User-interface testing - the testing of the user interface to ensure that it follows accepted standards and meets its requirements. User-interface testing is often referred to as graphical user interface (GUI) testing.