Searcharxiv⌕ Search
Home/Archive/arXiv

arXiv · 2402.01480

Selenium-Jupiter: A JUnit 5 extension for Selenium WebDriver

Boni García·Carlos Delgado Kloos·Carlos Alario-Hoyos·Mario Munoz-Organero
View original source ↗Read source document ↗Export metadata ↓

Abstract

Selenium WebDriver is a library that allows controlling web browsers (e.g., Chrome, Firefox, etc.) programmatically. It provides a cross-browser programming interface in several languages used primarily to implement end-to-end tests for web applications. JUnit is a popular unit testing framework for Java. Its latest version (i.e., JUnit 5) provides a programming and extension model called Jupiter. This paper presents Selenium-Jupiter, an open-source JUnit 5 extension for Selenium WebDriver. Selenium-Jupiter aims to ease the development of Selenium WebDriver tests thanks to an automated driver management process implemented in conjunction with the Jupiter parameter resolution mechanism. Moreover, Selenium-Jupiter provides seamless integration with Docker, allowing the use of different web browsers in Docker containers out of the box. This feature enables cross-browser testing, load testing, and troubleshooting (e.g., configurable session recordings). This paper presents an example case in which Selenium-Jupiter is used to evaluate the performance of video conferencing systems based on WebRTC. This example case shows that Selenium-Jupiter can build and maintain the required infrastructure for complex tests effortlessly.

Explore related subjects

cs.OH

Keep this discovery

BibTeXRIS

Boni García, Carlos Delgado Kloos, Carlos Alario-Hoyos, Mario Munoz-Organero. 2024-02-01. Selenium-Jupiter: A JUnit 5 extension for Selenium WebDriver. https://doi.org/10.1016/j.jss.2022.111298

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related papers

arXiv2026

Circular Economy Synergies and Trade-offs in Data Centres

This report analyses data centre (DC) sustainability and circularity, revealing existing synergies and trade-offs: The PUE is too coarse, mixing cooling and power provisioning. It wrongly attributes server fan consumption and transformation losses to IT energy. It does not measure compute but infrastructure efficiency, which is already outstanding. Compute energy, however, is exploding. Better energy metrics for DCs would thus cover i) compute efficiency, ii) transformation efficiency, and iii) cooling overhead. Trade-offs exist between cooling energy and water as well as on-site and upstream water: Consuming water on-site lowers the cooling energy, which also lowers the water consumed upstream in power generation. For 'wet' electricity, there is little competition: It is worth spending more on-site energy to save both electricity and related upstream water. For 'dry' electricity, there is a trade-off. Waste heat recovery brings energy circularity but has limited uses and is not the same energy quality, a fact not reflected by current metrics. A better metric would consider the avoided energy through heat recovery instead of the amount recovered. Material circularity can be achieved by interpreting the 9R framework in the context of DCs. Circularity-enhancing measures can be categorised into product design, process design and business models, choice of materials, and operating conditions. Together, they have effects across all circularity levels. The relation between DCs and the power grid is complex. Modern DCs present new challenges for the grid. Mitigation includes battery storage and onsite generation. These measures have, in turn, further consequences, both beneficial and detrimental. They can offer grid flexibility as well as innovations in the field of energy. But they also bring noise, pollution, and GHGs, and compete with the energy sector for resources.

cs.OH↗
arXiv2026

Digital Twin Modeling of a Highly Automated Agricultural Tractor

In efforts to increase research efficiency and availability, a digital twin of our research tractor (AMX G-trac) is created, focusing especially on the CAN communication for data reading and actuation command following the ISOBUS protocol. Mevea Simulation Software is utilized as the foundation, providing the kinematic model and visuals, while Python is used to read and write CAN messages over a Kvaser CanKing virtual CAN channel. Various performance tests involving straight line and turning behavior are performed in both the digital twin simulation and in the real world to measure similarity. Results indicate that the Mevea model behaves very comparable in its lateral dynamics, often within 5-10 percent, but requires better data to fully capture the longitudinal aspects like acceleration. The final model described in this paper sets the table for a second iteration to include more tractor functions such as hydraulics and tractor-implement dynamics.

cs.OH↗
arXiv2026

Risk-based Design for Sustainability in Cloud Systems: Insights from an Experts' Survey

Cloud Systems' Sustainability is critical in Cloud Computing, especially with the growing demand in many industries. Sustainability risks in Cloud Computing can be tricky, mostly because of system complexity and their impact on performance. Thus, this research focuses on Risk-based design (RBD) and how it can support the early identification of possible risks for Cloud System Sustainability, as well as respective mitigation strategies of each risk. In order to successfully identify risks of Cloud System Sustainability, an Expert Survey is conducted including experts with different roles from different industries, to identify possible sustainability risks of a Cloud System on all different levels. Thematic analysis of the responses resulted in a categorization of risks, as well as in the identification of mitigation strategies and factors affecting each risk. Such findings can be helpful for researchers and practitioners that utilize RBD when building sustainable Cloud systems.

cs.OH↗