1.The content model for the WebApp is
reviewed to uncover errors. This
‘testing’ activity is similar in many respects to copy-editing for a written document.
2.The design model for the WebApp is reviewed
to uncover navigation
errors. Use-cases, derived as part of the analysis activity, allow a Web engineer to exercise each usage
scenario against the architectural
and navigation design.
3.Selected processing components and Web
pages are unit tested. When WebApps
are considered, the concept of the unit changes. Each Web page encapsulates content, navigation
links and processing elements
(forms, scripts, applets).
4.The architecture is constructed and
integration tests are conducted.
The strategy for integration testing depends on the architecture that has been chosen
•a linear, grid, or simple hierarchical
structure—integration is similar to conventional software
•mixed hierarchy or network (Web)
architecture — integration testing is similar to the approach used for OO systems.