]>

Table 6: Test automation categories affecting the software process in case OUs.

OU Category Automation application Role in software process Test automation strategy Automation development Automation tools Automation issues Case A GUI testing, regression testing Functionality verification Part of the normal test infrastructure General increase of application Individual tools, test suite, in-house development Complexity of adapting automation to test processes Case B Performance, smoke testing Quality control tool Part of the normal test infrastructure GUI testing, unit testing Individual tools, in-house development Costs of automation implementation Case C Functionality, regression testing, documentation automation Quality control tool Part of the normal test infrastructure General increase of application Test suite, in-house development Cost of automation maintenance Case D Functionality testing Quality control for secondary modules Project-related cases Upkeep for existing parts Individual tools Costs of automation implementation Case E System stress testing Quality assurance tool Part of the normal test infrastructure General increase of application Test suite Costs of implementing new automation Case F Unit and module testing, documentation automation QC, overall effect harmful Individual users Recently scaled down Individual tools Manual testing seen more efficient Case G Regression testing for use cases Quality assurance tool Part of the normal test infrastructure General increase of application Test suite Cost of automation maintenance Case H Regression testing for module interfaces Quality control for secondary modules Part of the normal test infrastructure General increase of application Test suite, in-house development Underestimation of the effect of automated testing on quality Case I Functionality testing Quality control tool Project-related cases Application pilot in development Proof-of-concept tools Costs of automation implementation Case J Automation not in use QA, no effect observed Individual users Application pilot in development Proof-of-concept tools No development incentive Case K Small scale system testing QC, overall effect harmful Individual users Recently scaled down Self-created tools; drivers and stubs Manual testing seen more efficient Case L System stress testing Verifies module compatibility Project-related cases Adapting automation to the testing strategy Individual tools, in-house development Complexity of adapting automation to test processes