Abstract
When a system is maintained, its automated test
suites must also be maintained to keep the tests up to
date. Even though practice indicates that test suite maintenance can be very costly we have seen few studies considering the actual efforts for maintenance of testware.
We conducted a case study on an evolving system
with three updated versions, changed with three different change strategies. Test suites for automated unit and functional tests were used for regression testing the extended applications. With one change strategy more changes were made in the tests code than in the system that was tested, and with another strategy no changes were needed for the unit tests to work.
suites must also be maintained to keep the tests up to
date. Even though practice indicates that test suite maintenance can be very costly we have seen few studies considering the actual efforts for maintenance of testware.
We conducted a case study on an evolving system
with three updated versions, changed with three different change strategies. Test suites for automated unit and functional tests were used for regression testing the extended applications. With one change strategy more changes were made in the tests code than in the system that was tested, and with another strategy no changes were needed for the unit tests to work.
| Original language | English |
|---|---|
| Title of host publication | The 20th IEEE International Conference on Software Maintenance |
| Publisher | IEEE - Institute of Electrical and Electronics Engineers Inc. |
| Pages | 438-442 |
| Publication status | Published - 2004 |
Subject classification (UKÄ)
- Computer Science