Following are some of the technical terms used in Testing:

1. Acceptance Testing: Acceptance testing is a testing which is done to check whether or not the requirement of the specification are fulfill or not.
2. Alpha Testing: It is one of the most common type of software testing. This testing takes place at developer's site. Alpha testing is testing which is done when development is about to complete.
3. Beta Testing: This testing is done after Alpha testing. In this testing, product is given to the testers for further testing.
4. Boundary Value Analysis: It is a software testing technique in which inputs are the boundary values. Product is tested by passing the boundary values as input.
5. Compatibility Testing: This testing is used to evaluate the compatibility of the application with computing environment.
6. Crash: Crash testing is the form of destructive testing. Usually performed to check the design standards of the product.
7. Exhaustive Testing: In this type of testing, all possible inputs are used for testing. Exhaustive testing is done for smaller projects. For bigger projects, Exhaustive testing is not possible.
8. Functional Testing: Functional Testing is a part of Black box testing. In this testing, tester is not much concerned about the coding section. Functional testing usually describes what system does and not "how system does".
9. Integration Testing: This testing is done after Unit testing. In this testing, modules, which are tested in Unit testing, are integrated and then tested whether the project is working well after combining the modules.
10. Interface Testing: This testing is used to assure the quality of the product and to evaluate whether the component pass data to one another correctly. Integration Testing is done by both development and testing teams.
11. Performance Testing: Performance testing is a general testing, used to determine how the system perform in terms of responsiveness and stability.
12. Regression Testing: This testing is done to assure whether any small change in the project, does not effect the project. This is done by retesting the complete project.
13. Review: A meeting during which the product is presented to project personnel, managers, users, customers, or other interested parties for comment or approval.
14. Risk: Difference between expected and actual result is risk.
15. Stress Testing: This testing is usually done to determine the upper limits of capacity of the system. This testing is done to determine the system's robustness in terms of extreme load.
16. Test Plan: It identifies test items, the features to be tested, the testing tasks, responsibilities, required resources. For example: test design, validation protocol.
17. Test Case: Documentation specifying inputs, predicted results, actual results and a set of execution conditions for a test item.
18. Unit Testing: Testing of a single module is known as Unit Testing. This is the initial phase of software testing phase.
19. Usability Testing: This is the testing which is done by users to evaluate the system performance.
20. Validation: Validation testing checks whether the system meets the requirement or not. This basically involves "our approach towards product quality". Validation always involves with executing the code.
21. Verification: This basically involves "our approach to check whether the product is build according to the specification". Verification is based on checking of documents and files.