Automated replay and failure detection for web applications
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
A case study of automatically creating test suites from web application field data
Proceedings of the 2006 workshop on Testing, analysis, and verification of web services and applications
Integrating customized test requirements with traditional requirements in web application testing
Proceedings of the 2006 workshop on Testing, analysis, and verification of web services and applications
Applying Concept Analysis to User-Session-Based Testing of Web Applications
IEEE Transactions on Software Engineering
Building test cases and oracles to automate the testing of web database applications
Information and Software Technology
Scalability issues with using FSMWeb to test web applications
Information and Software Technology
Test input reduction for result inspection to facilitate fault localization
Automated Software Engineering
Proceedings of the 2010 ACM Symposium on Applied Computing
Modeling consumer-perceived web application fault severities for testing
Proceedings of the 19th international symposium on Software testing and analysis
A test suite reduction approach based on pairwise interaction of requirements
Proceedings of the 2011 ACM Symposium on Applied Computing
Information and Software Technology
A case study on bypass testing of web applications
Empirical Software Engineering
Hi-index | 0.00 |
Automated cost-effective test strategies are needed to provide reliable, secure, and usable web applications. As a software maintainer updates an application, test cases must accurately reflect usage to expose faults that users are most likely to encounter. User-session-based testing is an automated approach to enhancing an initial test suite with real user data, enabling additional testing during maintenance as well as adding test data that represents usage as operational profiles evolve. Test suite reduction techniques are critical to the cost effectiveness of user-session-based testing because a key issue is the cost of collecting, analyzing, and replaying the large number of test cases generated from user-session data. We performed an empirical study comparing the test suite size, program coverage, fault detection capability, and costs of three requirements-based reduction techniques and three variations of concept analysis reduction applied to two web applications. The statistical analysis of our results indicates that concept analysis-based reduction is a cost-effective alternative to requirements-based approaches.