This simply checks that all links work and reach the
right
page. Curiously, this
cannot always be automated. While a tool will indicate which links fail, only a human will know
74
Manage Software Testing
if a clicked link arrives at the right page. Use this as an exercise to draw a spreadsheet of website
pages. This will give you an idea of the amount of work involved and the degree of test coverage
achieved. Dynamically-created links (such as on a news website) can be tested generically. When
compared with the html, such a spreadsheet can also reveal unhittable pages.
???
Bash the browser.
This is
not
recommended but without any specifications it is what you may
end up doing, at least until the test team understand how the system is supposed to work. It
consists simply of exploring what features the browser offers and activating every control
possible therein. This may at least give you the information you need to write a requirements
specification.
Overall website requirements specifications may have to be assembled and maintained by the test team
(if no one else will). Websites cost: no one pays out that sort of money and stays in business without a
pretty good idea of what they want. If nothing else, you will get ideas for scenario or transaction tests
from the memoranda, and position papers generated while the business tried to identify what it wanted.
If nothing else the graphic design people will have a brief: get a copy of that.
Pages:
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217