Regression testing minimization, selection and prioritization: a survey
By Shin Yoo, Mark Harman. Software testing, verification & reliability, 2012
1,620 citations recorded by the source corpus.
Subfields: Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/34811b5b64c7b5b228d1dd12735a8a8b09bd357e
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Information Systems
- Koushik Sen
- Sarah Nadi
- George C. Necula
- Wontae Choi
- Gordon Fraser
- Frank Tip
- Max Schäfer
- Aryaz Eghbali
In Software
- Koushik Sen
- Gordon Fraser
- Sarah Nadi
- Frank Tip
- Max Schäfer
- Aryaz Eghbali
- George C. Necula
- Wontae Choi
Citations in the corpus
- Guided GUI testing of android apps with minimal restart and approximate learning (2013, methodology): “McMaster and Memon [74] proposed a technique [118] for reducing the number of test cases in a test suite, but this technique does not reduce the size of each test case.”
- The strength of random search on automated program repair (2014, background): “More details on prioritization techniques have been listed in [43].”
- An Empirical Evaluation of Using Large Language Models for Automated Unit Test Generation (2023, background): “Ex-ploring test suite minimization techniques [54] to reduce the size of the generated test suite is an interesting avenue for future work.”
- A Survey on Metamorphic Testing (2016, background): “Furthermore, analogously to the concept of test suite mini-misation, where redundant test cases are removed from a suite as it evolves [147], the use of minimisation techniques to remove redundant metamorphic relations is an open problem where research is needed.”
- Neural Attribution for Semantic Bug-Localization in Student Programs (2019, neutral): “It will be an interesting future work to use it for arbitrary programs in the context of regression testing [30], i.”
- Usage, costs, and benefits of continuous integration in open-source projects (2016, methodology): “RQ8: We confirmed that continuously running CI takes a non-trivial amount of time (and resources), so the testing research community should investigate methods for faster build and test, similar to the ongoing efforts on TAP at Google [4, 33,34,51,52], Tools for Software Engineers (TSE) at Microsoft”