Static Script-Based Testing

Slide 7 of 15

Static Script-Based Testing

Also in the early 1990's more advanced capture/replay testing tools offered rich scripting languages and reporting facilities. Now the test script was a program. Scripting languages were needed to handle conditions, exeptions, and the increased complexity of software. Automated script development, to be effective, had to be subject to the same rules and standards that were applied to software development. Making effective use of any automated test tool required at least one trained, technical person - in other words, a programmer.
Test management tools helped manage all the artifacts from requirements and test design, to test scripts and test defects. Also, commercially available performance tools arrived to test the performance of the system. These tools tested stress and load-tested the target system to determine their breaking points.(from: Software testing and continuous quality improvement - William E. Lewis, Gunasekaran Veerapillai)
- test scripting= programming
- ad-hoc coverage
- no coverage measurement
+ automatic execution
+ auto regression testing
- fragile tests break easily?
(depends on design/abstraction level)
See also COVER overview