The Reduction Process for Change Type Cases to Consider
| dc.contributor.author | Makady, Soha | en_US |
| dc.contributor.author | Walker, Robert | en_US |
| dc.date.accessioned | 2014-09-03T18:35:57Z | |
| dc.date.available | 2014-09-03T18:35:57Z | |
| dc.date.issued | 2014-09-03 | |
| dc.description.abstract | Pragmatic reuse tasks can be validated by a custom record-and-replay (R&R) technique that transforms automated test suites to focus on the reused code, reducing the need to develop test suites manually; this technique has previously been reified in the Skipper tool. In general, R&R test suites have been criticized as lacking maintainability when the source under test evolves, but the literature contains no empirical evidence on the merits or faults of R&R unit tests relative to alternatives. The associated paper “Maintaining Record-and-Replay Test Cases within Pragmatic Reuse Scenarios” reports on an empirical study with industrial developers that: (1) evaluates whether R&R unit tests within pragmatic reuse tasks are harder to maintain than ones written manually, and (2) investigates how developers would validate pragmatic reuse tasks in the absence of R&R tests. This technical report describes details of the process for reducing the number of cases to be considered to a manageable number. | en_US |
| dc.description.refereed | No | en_US |
| dc.identifier.department | 2014-1061-12 | en_US |
| dc.identifier.doi | http://dx.doi.org/10.11575/PRISM/31124 | |
| dc.identifier.uri | http://hdl.handle.net/1880/50214 | |
| dc.language.iso | eng | en_US |
| dc.publisher.corporate | University of Calgary | en_US |
| dc.publisher.faculty | Science | en_US |
| dc.subject | Record-and-Replay Test Cases | en_US |
| dc.subject.other | Pragmatic Reuse Scenarios | en_US |
| dc.title | The Reduction Process for Change Type Cases to Consider | en_US |
| dc.type | technical report | en_US |
| thesis.degree.discipline | Computer Science | en_US |