Prev | Current Page 187 | Next

Peter Farrell-Vinay

"Manage Software Testing"

In practice
however much of their function can be subsumed into:
??? A test process model showing the inputs and outputs of the test process, the tools supporting it,
the inputs to metrics, and the subprocesses
??? Test tools (in practice much paper otherwise used to write test specifications on can be saved by
using a good test management tool preferably with a built-in bug management tool)
??? Templates for creating documents with checklists for reviewing documents against
65
5
Testing and the Web
The web is another example of a disrupting technology (like RAD and XP) requiring that a lot of old
lessons get relearned. These lessons are:
??? All approaches to non-trivial software development require disciplined and trained practitioners.
??? Any information which isn??™t written down gets forgotten.
??? Users can??™t read code, don??™t very much like diagrams, and need some specification to sign off
before they??™ll part with their money.
??? Changes have ripple effects throughout systems.
??? Developers, testers, and test managers need to have some objective way of deciding if a bug exists.
??? If developers want to take a risk, and try and integrate a system in a big bang they are simply
ignoring 60 years of experience, and will eventually realize that unit and integration testing reduce
risk, and save time.
Early web development was characterized by many programmers quickly hacking simple static websites
with minimal features and quite terrible graphics, using simple tools.


Pages:
175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199