# @axinom/mosaic-e2e-ui-selectors

> Component models for testing Axinom Mosaic applications with Playwright.

Latest version **0.16.12** (published 2026-09-11) · PROPRIETARY license · 0 weekly downloads

## Install

```sh
npm install @axinom/mosaic-e2e-ui-selectors
pnpm add @axinom/mosaic-e2e-ui-selectors
yarn add @axinom/mosaic-e2e-ui-selectors
bun add @axinom/mosaic-e2e-ui-selectors
```

## Health

**Score 65/100 (B)** — status: active.

Positive: has types; esm support; no vulnerabilities; recently updated; high maintenance score.

Warnings: low downloads; pre 1.0.

## Facts

| | |
|---|---|
| Version | 0.16.12 |
| Published | 2026-09-11 |
| First published | 2022-08-16 |
| Weekly downloads | 0 |
| License | PROPRIETARY |
| TypeScript types | bundled |
| Module format | ESM + CommonJS |
| Node | >=20.19.0 |
| Dependencies | 0 |
| Unpacked size | 541.4 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Axinom |
| Maintainers | schwendner, axinom_kuzmin, ruwanx, axinomnpm |
| Keywords | axinom, mosaic, axinom mosaic |

## Links

- npm: https://www.npmjs.com/package/@axinom/mosaic-e2e-ui-selectors
- npm.io page: https://npm.io/package/@axinom/mosaic-e2e-ui-selectors

## Recent versions

- 0.16.12 (latest) — 2026-09-11
- 0.16.16-rc.4 (prerelease) — 2026-10-18
- 0.16.15 (next) — 2026-10-09
- 0.16.16-rc.3 — 2026-10-16
- 0.16.16-rc.1 — 2026-10-09
- 0.16.16-rc.0 — 2026-10-09
- 0.16.13-rc.9 — 2026-10-09
- 0.16.13-rc.6 — 2026-10-08
- 0.16.13-rc.5 — 2026-10-08
- 0.16.13-rc.3 — 2026-09-15
- 0.16.13-rc.2 — 2026-09-15
- 0.16.13-rc.1 — 2026-09-15
- 0.16.13-rc.0 — 2026-09-14
- 0.16.12-rc.9 — 2026-09-11
- 0.16.12-rc.8 — 2026-09-10
- … 686 more at https://npm.io/package/@axinom/mosaic-e2e-ui-selectors/versions

## README

# @axinom/mosaic-e2e-ui-selectors

## About the Package

This package is part of the Axinom Mosaic development platform. More information
can be found at https://portal.axinom.com/mosaic.

This library models components in the Mosaic UI library, `@axinom/mosaic-ui` for
use in Playwright tests. Exported class `UiWorkflowsModel` provides a model to
navigate the DOM tree and to perform operations and assertions with Playwright.

This library should be used to model customized services. It should be used in
concert with `@axinom/mosaic-page-models` which models the Mosaic management
system including the shell UI and managed services.

## License

This package can be licensed under the
[Axinom Products Licensing Agreement](https://portal.axinom.com/mosaic/contracts/products-licensing-agreement)
or evaluated under the
[Axinom Products Evaluation Agreement](https://portal.axinom.com/mosaic/contracts/products-evaluation-agreement).  
No part of Axinom's software may be copied, modified, propagated, or distributed
except in accordance with the terms contained in the Axinom Products Licensing
Agreement and Axinom Products Evaluation Agreement.

## Library Conventions

Many conventions should be obvious from reading the code. Still, for clarity
there are some, maybe less obvious, conventions described here. The library is
designed to leverage the capabilities of intellisense to guide a test author and
to minimise the need to refer to documentation and source. Conventions are
designed to foster intuition in the user, and to improve readability of tests.

- All models are extended from the `ComponentModel` class.
- If the desired functionality of an element can be achieved with a `Locator`
  then return a `Locator` rather than modelling behavior through additional
  methods and properties.

Exposing `Locators` empowers the test author, e.g. by enabling expressive
`expect` statements which wait gracefully. There are exceptions to the rule,
e.g. where an element is a generic container that could contain any other UI
components, a `ComponentModel` can be more flexible as it has the `getChild`
method.

- Classes extending `ComponentModel` should mirror components defined in the UI
  library where possible. The naming and structure should be aligned.
- Method parameters should be simple. Preferably just strings and numbers with
  sufficient doc comments to guide the user.

Enums and typed objects as parameters are good for enforcing type safety but
they require an additional level of introspection when authoring tests. If a
test fails due to a string typo its easy to fix. If there is a limited set of
options which can be codified, consider a method for each so that intellisense
will list them alongside other methods and properties (e.g. see
`UntypedFormField`).

---
_Source: https://npm.io/package/@axinom/mosaic-e2e-ui-selectors · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._