Automated testing is a fundamental practice in modern software development, ensuring software quality and enabling continuous integration and delivery. While unit, integration, and system testing are well-established and tightly integrated into development workflows, the automated assessment of web user interfaces (WUI) is often conducted with separate tools and manual processes. This separation leads to delayed feedback, reduced testing frequency, and increased effort in identifying and resolving UI-related issues. As a result, the quality of the user interface is typically assessed only intermittently rather than continuously throughout the development lifecycle.

This thesis aims at designing and implementing an approach for integrating automated web user interface assessment directly into developer workflows. The goal is to enable seamless triggering of UI assessments during development activities, such as within continuous integration pipelines or from within development environments. A suitable solution needs to provide an architecture for workflow-based integration, mechanisms for triggering assessments, and approaches for presenting results in an actionable and developer-friendly manner. The implementation should be based on an existing UI assessment backend and demonstrate how continuous UI quality evaluation can be embedded into established development practices, taking into account the diversity of assessment output formats, explanations and guidance in selecting assessment models and in interpreting assessment results as well as presenting the results of previous assessments in an integrated way linked with the changes.

The objective of this thesis is the creation of a solution or the combination of existing approaches to solve the problem of integrating automated UI assessment into developer workflows through an architecture and infrastructure as described above. This comprises the analysis of the state of the art in automated UI testing and developer tooling, as well as the demonstration of the solution by prototypical implementation and a suitable empirical evaluation. The evaluation should be based on a study with software developers, including a comparative analysis of different execution scenarios, and should assess effectiveness, efficiency, user satisfaction, and cognitive load using both quantitative and qualitative methods.