The baseline of the test is the interface
and features specification provided by the bank. See section 5.5.3.
??? The legacy application tests will (hopefully) be those originally created for the legacy applications
which have been thereafter maintained The baseline of the test is the set of requirements specifi-
cations from which the applications were developed. See section 5.5.6.
From this the value of identifying all the interfaces employed is evident. Fortunately many of these are
identified in the CGI, and various APIs, but interfaces with the legacy applications need to be identified,
and specified. All the elements in this architecture have interfaces. These need to be recorded to simplify
integration and system testing. See section 8.4.
Those experienced in web development will know that many of the specifications mentioned above
as baselines will not exist. The degree to which they
do
exist is evidence of the recognition of the risk
the company runs in developing the site. Note that insofar as the information can be obtained unambiguously
and easily from code, that is a sufficient baseline.
5.5.1 Website System Test Approaches
Since web pages can be put together fast using specialized tools, the temptation to make on-the-fly
changes has meant that there is no clear distinction between unit (or developer) tests and system tests.
Understanding what might go wrong depends to a large extent on testers having an intimate knowledge
of the code.
Pages:
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215