QA Glossary continued

In continuation to my last post,I have come up with some other terms and their meanings:

• Alpha Testing: Testing performed at the developer's site by a group that is independent of the design team and all the issues so found are fixed before going into production.
• Beta Testing: Testing performed at customer's site by one or more end users in order to know how good a software is,whether they should go into the production with this software or not. The software has to meet the acceptance criteria as set by the customer.
• Software testing methodology: It is a three step process: a) Creating a test strategy b) Creating a test plan c) Executing tests.
• Test strategy: The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.
• Clear box testing: Same as white box testing. It is a testing approach that examines the application's program structure, and derives test cases from the application's program logic.
• Boundary value analysis: Boundary value analysis is a technique for test data selection. A test engineer chooses values that lie along data extremes. Boundary values include maximum, minimum, just inside boundaries, just outside boundaries, typical values, and error values. The expectation is that, if a systems works correctly for these extreme or special values, then it will work correctly for all values in between. An effective way to test code, is to exercise it at its natural boundaries.
• Ad hoc testing: Random testing which is performed with no formal documents so it is a least formal testing approach.