Skip to content

Evaluating Automated Testing on an Open-Source Web Application Using Cypress

Aug 2026 · 0 citations · 19 references
Computer Science

TL;DR

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.

View source

Similar papers

Open access Jul 2026

Implementasi Automation Testing End-to-End Menggunakan Cypress pada Web E-Conference Parisada serta Evaluasi Efisiensi Pengujian

Manual testing on interactive applications such as web e-conferences often faces constraints in the form of human error and long execution durations, especially in repetitive regression processes. This research aims to implement automated end-to-end (E2E) testing using the Cypress framework and evaluate the level of testing time efficiency on the Parisada platform. The research methodology includes designing core functionality scenarios covering the authentication process, system navigation, meeting room creation, and communication session termination. Testing was conducted through three trials (P1, P2, P3) to simulate various inhibiting variables, such as unstable network latency and user familiarity levels with the application interface. The results showed that all automated testing scenarios successfully achieved a 100% pass rate. In terms of efficiency, the use of Cypress significantly reduced the execution duration from an average of 60.0 seconds in manual testing to only 23.67 seconds in automated testing. Data analysis indicates an average time efficiency increase of 60.55%. Automated testing also proved to be more consistent and reliable in dealing with technical fluctuations compared to manual testing. In conclusion, 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 · 0 citations
Conference Open access Jul 2026

Automating End-to-End Test Suite Design for Microservices with Large Language Models

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 · 0 citations
Review Jul 2026

TestMiner: Software Testing Analysis for GitHub Repositories

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
Book Open access Jul 2026

Can LLMs Make Software Testing Greener? An Empirical Study on JUnit Test Energy Reengineering

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 · 0 citations
Open access Aug 2026

Automated Black-Box and Manual Basis Path Testing on E-OBE Application

In the current digital era, the development of academic mobile applications, such as the E-OBE application used by Universitas Trunojoyo Madura, requires rigorous testing to ensure robustness and reliability. However, manual testing is often inefficient for detecting complex backend issues and input-handling weaknesses within modern REST API architectures. Objectives: This study aims to evaluate the structural complexity and external robustness of the E-OBE mobile application's backend using a combined testing approach. Methods: The research utilizes White-Box testing, implementing the basis path technique to manually measure the cyclomatic complexity of selected system controllers. Simultaneously, automated Black-Box testing is executed via EvoMaster, targeting REST API endpoints configured with an OpenAPI schema to generate extensive test cases. Results: The White-Box testing revealed that the cyclomatic complexity of the evaluated controller functions ranges from 1 to 5, indicating a relatively simple control flow within the examined source code. Conversely, the automated Black-Box testing (where the optimal run generated 49 HTTP calls and 47 JUnit tests) detected 27 distinct fault manifestations. These unique faults were predominantly API response schema mismatches (22 occurrences), server errors (HTTP 500) (4 occurrences), and an authentication issue (1 occurrence). Conclusions: 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. The API documentation and external input validation require significant improvements to resolve mismatches and prevent server crashes, ensuring better reliability for future front-end integration.

Abdul Azis Naufal Farizqi, Made Hanindia Prami Swari, I. G. S. Mas Diyasa · 0 citations
Book Open access Jul 2026

Testing AIware Systems: A Software Engineering Survey

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 · 0 citations

Related blog posts

MIT News · Artificial Intelligence Aug 17, 2026

Q&A: Rethinking how innovation happens

In his latest book, Professor Eugene Fitzgerald examines the forces that turn breakthroughs into value — and why innovation resists simple formulas.