5.5.2 Browser Tests
Web test specifications sometimes derive from attention to the code and the bugs it may exhibit. Testers being
in the position of men with only a large nail of a web to test, and no hammer of a requirements specification
or other baseline, will look for whatever hammers are to hand, and will read the raw code if nothing else.
The danger with such an approach is that:
??? It may deteriorate into a browser-bashing session in which testers unsystematically attack every
screen element presented.
??? It doesn??™t allow for potential state changes or subtle feature interactions which ???real??? transactions
may cause.
There is a large number of tools available to check the html. Servlets and applets will need to be unit
tested. In this respect, as in many others, there is little difference between web, and any other kind of testing.
5.5.3 Web Server Tests
The server-based components do things such as:
??? Security checks
??? Order processing
??? Credit checking and payment processing
??? Business logic (possibly using a separate set of business rules) to interact with a database
??? Creation of
live
pages possibly using ASP or JSP
These require a system test but without a UI. Consider using a unit-test tool to interface with the
components. Once you have a way of bypassing the lack of the UI you can execute what are in effect
system tests of the features of each of these subsystems and end-to-end tests of the various scenarios.
Pages:
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218