Software reconnaissance: mapping program features to code
Journal of Software Maintenance: Research and Practice
Formal Concept Analysis: Mathematical Foundations
Formal Concept Analysis: Mathematical Foundations
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Locating Features in Source Code
IEEE Transactions on Software Engineering
Assessing test-driven development at IBM
Proceedings of the 25th International Conference on Software Engineering
Locating Program Features using Execution Slices
ASSET '99 Proceedings of the 1999 IEEE Symposium on Application - Specific Systems and Software Engineering and Technology
Test-Driven Development as a Defect-Reduction Practice
ISSRE '03 Proceedings of the 14th International Symposium on Software Reliability Engineering
Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods
IEEE Transactions on Software Engineering
Can LSI help Reconstructing Requirements Traceability in Design and Test?
CSMR '06 Proceedings of the Conference on Software Maintenance and Reengineering
IEEE Transactions on Software Engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Towards traceable test-driven development
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
A Systematic Survey of Program Comprehension through Dynamic Analysis
IEEE Transactions on Software Engineering
Improving automated requirements trace retrieval: a study of term-based enhancement methods
Empirical Software Engineering
Tracing requirements to tests with high precision and recall
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Hi-index | 0.00 |
Requirements traces establish links between requirements and software artifacts, such as source code, test cases and configuration files. Understanding which requirements are covered by test cases, i.e. requirements tracing in test cases, is an important concern in quality assurance of complex software systems. There is existing literature to obtain requirements traces in different software artifacts. In this work, we build upon existing requirements tracing methods for test cases and introduce test intents, i.e. which requirements test cases aim to test. We also propose a method to identify test intents, and show that our approach can identify the intents successfully on our case studies on four realistic software systems.