This can be done either through a paid
service or using shareware tools. You need to check:
??? Availability: is the website visible? (Can it be pinged?)
??? Linkrot: ensure that all the links in your site are always current and that any hosted links are
themselves current.
??? Link speed checks: to ensure that the page can be speedily reached.
??? Download: that downloads are fast and correct.
??? Back-end connections: do calls to legacy and web applications succeed? Are databases unduly
slow? (Because they are very big?)
??? Memory leaks: is there any evidence? Which database drivers are you using?
??? Traffic volume: is this increasing unduly?
??? Click-out rates: are users abandoning your website as soon as they find it?
??? Security alerts: are all your systems upgraded to counter the latest threats?
83
6
The Overall Test
Life-Cycle
We need a test process that is closely integrated with whatever software life-cycle the project believes it
is using and that brings discipline to the manner in which the what-to-test, when-to-stop, and whodoes-
what questions are answered. Testing requirements at each phase of the project have to be defined.
The cycle shown in Figure 6.1 is very simple, obvious, and true for (almost) any kind of test.
1
If it doesn??™t
happen, you have a problem.
A typical software life-cycle contains the following activities, not necessarily in the order shown here:
??? Initiate, plan, and set up infrastructure
??? Write the requirements
??? Design the architecture
??? Code and unit test
??? System test
??? Document and train,
??? Install, cutover, support, and evolve
2
As test manager you need to relate these activities to the life-cycle being used as discussed in section
4.
Pages:
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231