A methodology for controlling the size of a test suite
ACM Transactions on Software Engineering and Methodology (TOSEM)
In black and white: an integrated approach to class-level testing of object-oriented programs
ACM Transactions on Software Engineering and Methodology (TOSEM)
Analysis and testing of Web applications
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Operational Profiles in Software-Reliability Engineering
IEEE Software
Object-Based Data Flow Testing of Web Applications
APAQS '00 Proceedings of the The First Asia-Pacific Conference on Quality Software (APAQS'00)
A Graphical Class Representation for Integrated Black- and White-Box Testing
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Bi-Criteria Models for All-Uses Test Suite Reduction
Proceedings of the 26th International Conference on Software Engineering
Composing a Framework to Automate Testing of Operational Web-Based Software
ICSM '04 Proceedings of the 20th IEEE International Conference on Software Maintenance
A Scalable Approach to User-Session based Testing of Web Applications through Concept Analysis
Proceedings of the 19th IEEE international conference on Automated software engineering
Leveraging User-Session Data to Support Web Application Testing
IEEE Transactions on Software Engineering
ICSM '05 Proceedings of the 21st IEEE International Conference on Software Maintenance
Automated replay and failure detection for web applications
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
Analysis of test suite reduction with enhanced tie-breaking techniques
Information and Software Technology
Hi-index | 0.00 |
Existing test suite reduction techniques employed for testing web applications have either used traditional program coverage-based requirements or usage-based requirements. In this paper, we explore three different strategies to integrate the use of program coverage-based requirements and usage-based requirements in relation to test suite reduction for web applications. We investigate the use of usage-based test requirements for comparison of test suites that have been reduced based on program coverage-based test requirements. We examine the effectiveness of a test suite reduction process based on a combination of both usage-based and program coverage-based requirements. Finally, we modify a popular test suite reduction algorithm to replace part of its test selection process with selection based on usage-based test requirements. Our case study suggests that integrating program coverage-based and usage-based test requirements has a positive impact on the effectiveness of the resulting test suites.