5.3 Test Scripts
Manual test scripts are best kept in a test management tool. Alternatively they can be prepared in a
spreadsheet for later importation into a test management tool. Automated test scripts need to be reviewed
and configuration-managed. Both manual and automated scripts can be reused by being assembled into
???runs??? or batches, covering a set of objectives, a use case, or a scenario.
Keep test scripts configuration-managed: you may find that you may need more than one version of
each in order to create different test packs for different releases.
7.6 Bug Management Process and Tool
The bug-management process (Figure 7.2) will typically have 7 stages. All should be tool-supported:
1.
Execute tests or reviews.
Testers run system and/or unit tests and gather results. Note that it is
usually pointless bureaucracy to record unit test failures of the unit tests executed by developers.
Only when a unit test fails on submission to configuration management is it worth recording.
The unit tests should occur before the unit is submitted for configuration management and the
unit should never be admitted if the unit fails.
102
Manage Software Testing
FIGURE 7.2
Bug management process
Start/stop
Execute tests
Identify and record a bug
Review and triage the bug
Assign the bug
Change the code
Unit-test the code
Submit code and unit
tests for a build
Retest bugs
Manage the bug
management tool
Bug
management tool
Build
management tool
Bug
management tool
Test database
Test database Tests
Initial bug details
Rejected bug
Assigned bug details
Code
Unit tests
Code and unit tests
Build
System tests
Bug report
Bug/build details
Edits
Retest failed bug
report
Configuration
management tool
Reports
Defect charts
Defect logs
Testing Processes and Infrastructure
103
2.
Pages:
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267