Posts Tagged ‘Functionality Testing’
PDCA Cycle and Classes of Reviews:
PDCA Cycle:
Plan (P): Device a plan. Define your objective and determine the strategy and supporting methods required to archive the objective.
Do (D): Executing the plan. Create the conditions and perform the necessary training to execute the plan.
Check (C): Check the results to determine whether work is progressing according to the plan and whether the results are obtained.
Action (A): Take the necessary action. If your check up reveals that the work is not being performed according to plan or results an not what was anticipated device measures for appropriate action.
Classes of Reviews:
1. Informal Review:
Ø Generally one to one meeting
Ø No agenda
Ø Results are not formally reported
Ø Occurs as needed throughout each phase.
2. Semi Formal Review:
Ø Facilitated by the author (the person who is responsible for the activity)
Ø Presentation is made with comment throughout and at the end
Ø Reports are distributed to the participants
Ø Possible solutions for defect not discussed
Ø Occur one or more times during phase.
3. Formal Reviews:
Ø Facilitated by the modulator (the person who has link between test engineer and Management)
Ø Assisted by a recorder
Ø Meeting are planned in advance
Ø Directly dependent on the preparation of participants.
Importance of Web Site Testing
The web is a powerful medium, through which any person or organization can publish its message for consumption or use by anyone who has access. Part of the value of the web is that content can be easily modified or added to as a message grows or changes. However, the downside to this non-permanence is the idea that the message or site does not need to be perfect before it is presented to the intended audience and participants. This is not a productive school of thought. We must realize that a website should be treated similar to any other marketing or informational piece and thoroughly reviewed for correct content and functionality through formal quality control procedures.
If you want a great Web site, you must test its usability. Just because no one has complained about your site doesn’t mean that all your visitors are using your site effectively, efficiently and to their full satisfaction.
Visitors won’t make the effort to complain unless you have outraged them in some way, or have provided an easy way for them to in touch with you from every page about the problems they may be having.
Who should be testing the website? The client? The development team? A third party? The answer is, “Yes, to all three.” Quality control personnel should consist of the client, the development team members and other personnel who are not involved with the creation of the site. This ensures that the site is reviewed by a variety of different people who have different relationships to – and expectations of – the site.
