The experimental results show that the Cypress-based end-to-end test suite has short and stable execution times, and resilient data-cy attributes significantly reduce maintenance overhead when UI changes occur.
Abstract
End-to-end automated testing is increasingly used in web software development to ensure system quality and shorten response times during development. However, the true effectiveness of automated testing depends on many factors including execution time, stability of test results, and maintainability of the test suite as the application continues to evolve. In this paper, we evaluate the effectiveness of end-to-end automated testing using the Cypress framework for an open-source web application. We deployed the experiment with 27 test cases. The test's effectiveness is measured by execution speed, reliability, and maintainability. The experimental results show that the Cypress-based end-to-end test suite has short and stable execution times. It suits frequent runs during software development. The majority of test cases achieved consistent results across multiple runs, while flakiness only occurred in a few tests which involve complex interactive functions. Furthermore, the study highlights the impact of element locator strategies and Page Object Model (POM) architecture on test suite maintainability, demonstrating that resilient data-cy attributes significantly reduce maintenance overhead when UI changes occur.
The transition to automation testing using Cypress has proven highly effective in accelerating the quality assurance (QA) cycle and maintaining continuous software functionality stability on the Parisada application.
Raditya Aria, Eri Haryanto, Ryan Ari Setyawan· Infotek : Jurnal Informatika...· 0 citations
Graphical user interface (GUI) tests are used to validate end-to-end business flows. In microservice-based systems, a single user action may trigger a chain of inter-service calls, which require verification. In practice, end-to-end test suite design is largely manual and hard to maintain. We propose a multi-agent workflow that takes as input use cases, microservice interface specification, architecture documentation, and a GUI description, and produces executable Selenium tests with test oracles. We evaluate the approach on open-source microservice systems by comparing the generated suites with manually created benchmarks. During test execution, we collect execution traces to evaluate the coverage of microservice endpoints. In addition, we evaluate the fault detection capability of the generated test suites by seeding faults into the systems under test.
E. Ovsiannikova, D. Truscan· Annual International Compute...· 0 citations
Software systems have unique testing characteristics. Some projects can emphasize unit tests, while others may focus on end-to-end testing. Test organization may vary across ecosystems: in languages like Python and Java, tests are typically placed in dedicated folders, whereas Go and Rust projects commonly co-locate tests with source code. These distinctions make it harder to understand how a project approaches testing. In this paper, we present TestMiner, a tool for exploring software testing in GitHub repositories. TestMiner provides an overview of a project's testing practices, including test statistics, test location, test metrics across releases, and dependencies related to testing. We used TestMiner in an undergraduate Software Testing course, where 50 students explored the testing practices of real-world GitHub repositories. Overall, students expressed positive feedback regarding TestMiner. They were able to critically explore a variety of testing practices, including test organization, test evolution, test fixtures, mocking, and edge-case testing. TestMiner is available at: https://andrehora.github.io/testminer. Screencast: https://youtu.be/w1sBgLTq-7Y.
André C. Hora, José Miguel Rojas, Romain Robbes· 0 citations
Software testing is essential to ensure the reliability of software. To that end, test suites are often executed repeatedly, due to frequent developer validation runs, and practices like continuous integration. This repeated execution leads to substantial energy consumption and thus potential environmental impact. In this paper, we conduct an exploratory study to examine whether current Large Language Models (LLMs) are capable of reengineering unit tests to improve their energy efficiency while maintaining test effectiveness. Our results indicate that, using a straightforward prompt, only a small subset of unit tests shows improved energy efficiency, with negligible impact on test effectiveness. Subsequently, we scrutinize our results for potential reasons for the relatively low number of energy-reengineered unit tests. We observe that energy efficiency related information is scarce on prominent platforms like StackOverflow and GitHub. This scarcity of information potentially affects how LLMs can be trained on the topic of energy efficiency.
Xutong Liu, Andy Zaidman· SIGSOFT FSE Companion· 0 citations
The evaluated controller functions of the E-OBE application exhibit simple structural complexity, however, the automated testing revealed significant input-handling weaknesses and schema inconsistencies, ensuring better reliability for future front-end integration.
Abdul Azis Naufal Farizqi, Made Hanindia Prami Swari, I. G. S. Mas Diyasa· bit-Tech· 0 citations
Overall, this survey provides a structured characterization of the current state of AIware testing research and identifies key structural challenges that must be addressed to support lifecycle-aware, reliable AIware systems.
K. Gonzalez, Mariam El Mezouar· AIware· 0 citations
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduAug 17, 2026
A USAF cadet and a Lincoln Laboratory researcher found AI chatbots can help nontechnical service members produce viable software applications for their unique problems.
