b. A set of tests can be related to a particular build and archived off.
c. Someone else can run that suite other than the person who wrote it.
d. A regression suite and set of smoke and confidence tests are identified and maintained.
7.4.6 What It??™ll Cost Us to Automate Our Tests
The cost of test automation can be broken down thus:
??? The cost of assessing the tools on the market
??? The cost of the tool
??? The cost of training staff to use the tool
??? The cost of creating the automated tests
??? The cost of maintaining the automated tests
??? The (possible) cost of a code profiling tool
??? The cost of having a special build for use with the code profiling tool
??? The cost of assessing the results
??? The cost of integrating that tool into whatever dashboard you want to run your tests with
7.4.7 How We??™ll Know if We??™ve Automated Our Tests Successfully?
??? When we can show that our test suite exercises all the code (apart from those error messages best
tested by hand)
100
Manage Software Testing
??? When we can show that our test suite exercises 100% of the features
??? When the test suite finds serious bugs
??? When the test suite can be run overnight
??? When the test suite can be reused for other scenarios than the ones you thought of at the start
??? When we have time at the end of the test cycle to investigate oddities better
7.4.8 Open Source GUI Test Tools
Freeware GUI test tools are primarily functional test harnesses except that they automate a graphical
user interface.
Pages:
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263