UUV - User centric Usecases Validator

Discovering your application by usecase validation

Make test writing fast, understandable by any human understanding English or French.

Benefits

If used correctly, integrates accessibility from the development stage
A living documentation is possible because we propose an unified language for developers and non-developers with a rich dictionary of ready-to-use sentences
@uuv/assistant that facilitates the writing of tests by suggesting the most accessible sentences
JetBrains Plugin that helps you to write and execute your UUV E2E tests from JetBrains IDEs
Integrates several runtime engines: Cypress / Playwright
User friendly and standardized execution report(example)
Comparison

Criteria	Cypress	Playwright	Testing library	UUV
User centrism	:x:	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:
Native accessibility	:x:	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:
Easy setup configuration for BDD test	:warning:	:warning:	:heavy_minus_sign:	:heavy_check_mark:
Understandable by everyone (included non dev)	:x:	:x:	:x:	:heavy_check_mark:

Syntax example

With this dom example :

<body>
<h1>Result<h1>
</body>

we see that the sentence proposed by UUV is the most understandable of all

Library	Syntax
Cypress	cy.get('h1').contains('Result')
Playwright	await expect(page.getByTitle('Result')).toHaveCount(1)
Testing library	expect(screen.getByTitle(/Result/i)).toBeTruthy()
UUV	Then I should see a title named "Result"

Documentation

Libraries

Concepts

The @uuv library (User centric Usecases Validator) is an ecosystem that simplifies the writing of End to End tests in a BDD approach and a user-centric way.

The problem

Automated software testing is a growing practice. It adds a better
level of quality on the code of an application by verifying non-regression or validating use cases.

The End to End test is a technique used to verify if an application (web,
mobile...) behaves as expected, from start to finish. It consists in verifying that the end user can complete the main usage scenarios of the application.

Unlike unit test which only aims to verifying the behavior of a function, or
the integration test which consists in making several modules of the application interact with each other in order to see their good cooperation, the End to End test allows to check from a browser (for example for web applications) the behavior of your application according to a set of use cases.

During the E2E test, the validations consist most of the time in checking the elements returned to the user via the web browser (DOM)

Therefore, several additional questions arise:

How to clearly express use cases?
For omnichannel applications, how to check your application on different browsers and devices?

uuv-e2e-accessibility-test

Popularity

What's Inside

README

UUV - User centric Usecases Validator

Discovering your application by usecase validation

Benefits

Comparison

Syntax example

Documentation

Libraries

Concepts

The problem

Confidence

Similar Plugins

test-automation-skills-agents

e2e-test-framework

e2e-runner

accessibility-testing

playwright-autopilot

Cypress