Validation Testing

Validation Testing

• Validation testing begins at the conclusion of integration testing,
• When individual components have been exercised, the software is completely assembled as a package, and interfacing errors have been uncovered and corrected.
• At the validation or system level, the distinction between conventional software, object-oriented software, and WebApps disappears.
• Testing focuses on user-visible actions and user-recognizable output from the system.
• In simple meaning, validation succeeds when software functions in a manner that can be reasonably expected by the customer.
• Validation-Test Criteria
• Software validation is achieved through a series of tests that demonstrate conformity with requirements.
• A test plan outlines the classes of tests to be conducted and A test procedure defines specific test cases that are designed to ensure that
• All functional requirements are satisfied,
• All behavioral characteristics are achieved,
• All content is accurate and properly presented,
• All performance requirements are attained,
• Documentation is correct, and usability and other requirements are met (e.g., transportability, compatibility, error recovery, maintainability).
• After each validation test case has been conducted, one of two possible conditions exist:
• The function or performance characteristic conforms to specification and is accepted.
• A deviation (Error) from the specification is uncovered and a deficiency list is created.
• Configuration Review :
• An important element of the validation processis a configuration review.
• The objective of the review is to ensure that all elements of the software configuration have been properly developed.
• The configuration review, sometimes called an audit…
• Acceptance Testing :
• When custom software is built for one customer, a series of acceptance tests are conducted to enable the customer to validate all requirements.
• Conducted by the end user rather than software engineers, an acceptance test can range from an informal “test drive” to a planned and systematically executed series of tests.
• In fact, acceptance testing can be conducted over a period of weeks or months.
• Alpha and Beta Testing :
• If software is developed as a product to be used by many customers, it is impractical to perform formal acceptance tests with each one. 
• Most software product builders use a process called alpha and beta testing to uncover errors that only the end user seems able to find.
• The alpha test is conducted at the developer’s site by a representative group of end users.
• The software is used in a natural setting with the developer “looking over the shoulder” of the users and recording errors and usage problems.
• Alpha tests are conducted in a controlled environment.
• The beta test is conducted at one or more end-user sites.
• Unlike alpha testing, the developer generally is not present. Therefore, the beta test is a “live” application of the software in an environment that cannot be controlled by the developer.
• The customer records all problems (real or imagined) that are encountered during beta testing and reports these to the developer at regular intervals.
• As a result of problems reported during beta tests, you make modifications and then prepare for release of the software product to the entire customer base.