Revised Test Plan (Assignment 3)

Test Plan

Alpha Testing: - Alpha Testing is a type of software testing performed to identify bugs before releasing the product to real users or the public. It is a type of Acceptance testing. it is done early on, near the end of the development of the software, and before Beta Testing. The main objective of alpha testing is to refine the project by finding (and fixing) the bugs that were not discovered through previous tests. alpha testing takes place in the test lab environment on a separate system. In this technique, the project manager teams up with the developer to define specific goals for alpha testing, and to integrate the results into evolving project plans. Methods of processing the Alpha testing • Review the design specification and functional requirements • Develop comprehensive test cases and test plan • Execute test plan • Log defects • Retest once the issues have been fixed Advantage of Alpha Testing is to Better insight about the software's reliability at its early stages and Free up your team for other projects.

Unit Testing of the Project The unit Testing process of the “project is a level of software testing where individual units/ components of a software are tested”. Because unit testing is primarily focussed on the implementation and requires an understanding of the design intent, it is much more efficiently done by the designers rather than by independent testers. “Experience has shown that unit-level testing (and reviewing) is very cost-effective. It provides a much greater reliability improvement for resources expended than system-level testing. It tends to reveal bugs which are otherwise insidious and are often catastrophic, like the strange system crashes that occur in the field when something unusual happens”. The test “strategy should identify the totality of testing which will be applied to the system − what types of testing will be performed, and how they will contribute to the overall quality and reliability of the product. A good test strategy will clearly scope each class of tests and assign responsibility for it. Typically, an organization will have some standard conventions to follow, but each project must identify aspects of the system which are critical or problematical, and clearly identify how these will be tested and by whom. Ultimately the Project Plan (or some form of Master Test Plan) for each project will define what needs to be covered by unit testing on that project. This type of information works well presented” in a checklist.

“unit testing is primarily focussed on the implementation, and requires an understanding of the design intent, it is much more efficiently done by the designers rather than by independent testers”.