The objective of testing is to ensure that the Web site is ready for operation. The test manager and the testing team have this responsibility. A Web test process will enable a tester or developer to meet critical assignment dates, minimize errors in testing, and improve the overall site.
It is important to realize when you select the process that it forces your test team and all parties involved to follow a precise process of testing. The Web test process builds on a unified process of requirements, analysis of the requirements, development, design, and site code.
If the Web test process is followed accurately, measurable results can be documented and presented to management and eventually the audit team. The V-process diagram illustrates the involvement of those associated with the testing process.
Requirements analysis. A specification that identifies the basic requirement functionality of the Web site.
Architectural design. A design specification that directs the designers in developing and laying out the Web site.
Detailed design. A detailed layout of the specifications that shows how each piece of the Web site will fit into place.
Code and unit test. The code is created and a unit test checks that specific segment of code.
Software integration. The process that allows the designer to set up the software and work with the design of the system.
System integration. The process that allows the designer to implement and begin the implementation of the system.
Acceptance test. The final phase of testing allows the user to put the Web site into production.