paypal.com) used both escrow accounts, and credit card authorizations to speed
web transactions
??? 1-Click?„? allows a user to simply click a button to authorize payment. This requires that the
browser has cookies on.
Both these approaches require similar flows to the one above for the purposes of getting the user
authorized. All approaches involve a lot of security issues most of which are hidden from the merchant??™s
website.
5.5.6 Legacy Application Tests
Some issues to be considered when testing legacy applications in the web:
1. There will (almost certainly) be no requirements or any other specifications. What you will be
offered is (possibly) a peek at the code. If the legacy application was bought from a supplier you
may not even get that.
2. The interface to the web may ignore little-used but essential features known only to the staff who
(rarely) used them. The people may already have left. Their absence of both the features and staff
will not be noticed until too late (Year-end accounts, leap-years, month-end reconciliations,
journaling).
In both these cases be prepared to fight for the use of a technical writer or literate tester, and the time
to get a requirements specification written. (You will be accused of empire-building, colonization of the
development process and worse.) The time you (and, ultimately everyone else) will save will outweigh
such considerations. Have the technical writer excavate all the memoranda, manuals etc.
Pages:
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222