Similarly the baseline of a server page
web unit test can be expressed as a decision table wherein some combination of page state (before test),
and input variables will lead to a page state (after test), expected outputs and expected results.
Drivers and stubs can be developed from such a baseline. A driver is built (probably using a scripted
test tool) to populate a client page??™s input forms and generate the test events. The driver page will include
some script functions and the Document Object Model (DOM) allows its interaction with the page
under test. Stubs can be developed either as client pages, server pages, or web objects. Their complexity
will depend both on the type of interaction between the page under test, the component to be substituted,
and on the internal complexity of the component(s).
Server pages are usually more complex than client pages due to scripting languages and such technologies
as ASP and JSP. Thus a server page can receive data from a client page through predefined objects,
manage a user session, redirect a session to other web pages, interact with other objects on the web
server, interface to a database or a file, and send or receive an e-mail.
5.5.9 Dynamic Server Page Creation
Dynamic Server Pages (DSP) can create a large number of page types thus complicating testing.
One solution is to use the rules contained in the DSP scripts to generate a number of tests each of
which is self-checking in that a user or a script can check the page contents against the page specifications
both of which are evident from the page.
Pages:
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225