The keywords represent
a very simple specification language that non-programmers may be able to use directly to develop
automated tests. You still need automation engineers to implement the things that the keywords do and
with that comes all the usual issues of GUI automation.
Keyword-driven tests tend to employ ???Wizards??? to create functions. These ???Wizards??? generate code.
If you want to maintain your functions or do anything clever with them you may still need to write code.
7.4.10 Libraries
Test-script maintenance can be reduced by creating a library of GUI object functions such as ???
open a
file
???,
???
Close a file
???,
and
???
Write to a field(x)
???;
thus, when the application changes, only the changed object??™s
function needs to be changed.
7.4.11 Data-Driven Tests
Most commercial tools allow you to create scripts and then populate them from a spreadsheet or database
with run-specific data such as ???employee name???, ???employee address???, etc. Each test run can thus simulate
the entry of different data. This is where test automation shows big RoI.
7.4.12 Multiple-Function Test Tools
A new generation of test tools can be used for unit, system, and performance tests. They can also be
used for HTML and link checking. This can save considerable time at the price of requiring some
organization.
Testing Processes and Infrastructure
101
7.5 Monitoring Test Progress
You have to deal with 6 issues when monitoring test progress:
1.
Pages:
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265