A Taxonomy of Information Attributes for Test Case Prioritisation: Applicability, Machine Learning

January 16, 2022 Β· Entered Twilight Β· πŸ› ACM Transactions on Software Engineering and Methodology

πŸ’€ TWILIGHT: Eternal Rest
Repo abandoned since publication

Repo contents: LICENSE, README.md, attributes, bib, docs, figs, references, taxonomy

Authors Aurora Ramírez, Robert Feldt, José Raúl Romero arXiv ID 2201.06044 Category cs.SE: Software Engineering Cross-listed cs.AI Citations 9 Venue ACM Transactions on Software Engineering and Methodology Repository https://github.com/tepia-taxonomy/taxonomy-analysis ⭐ 1 Last Checked 2 months ago
Abstract
Most software companies have extensive test suites and re-run parts of them continuously to ensure recent changes have no adverse effects. Since test suites are costly to execute, industry needs methods for test case prioritisation (TCP). Recently, TCP methods use machine learning (ML) to exploit the information known about the system under test (SUT) and its test cases. However, the value added by ML-based TCP methods should be critically assessed with respect to the cost of collecting the information. This paper analyses two decades of TCP research, and presents a taxonomy of 91 information attributes that have been used. The attributes are classified with respect to their information sources and the characteristics of their extraction process. Based on this taxonomy, TCP methods validated with industrial data and those applying ML are analysed in terms of information availability, attribute combination and definition of data features suitable for ML. Relying on a high number of information attributes, assuming easy access to SUT code and simplified testing environments are identified as factors that might hamper industrial applicability of ML-based TCP. The TePIA taxonomy provides a reference framework to unify terminology and evaluate alternatives considering the cost-benefit of the information attributes.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering