A command-based guide for writing Playwright end-to-end tests, which check a widget through its complete browser workflow, for a Mendix web widget monorepo, a repository containing multiple related packages.

Creating or improving Playwright specs for pluggable widgets, including navigation, locators, assertions, and snapshots.

It points developers to the project's testing rules and helps them discover the real page names, menus, and selectors before writing tests.

How mendix/web-widgets configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to mendix/web-widgets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/mendix/web-widgets/main/.claude/commands/mendix/e2e-spec.md

Clone the repo

git clone --depth 1 https://github.com/mendix/web-widgets

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mendix/web-widgets/e2e-spec/github.svg)](https://agentmods.dev/commands/mendix/web-widgets/e2e-spec)

Your own site

<a href="https://agentmods.dev/commands/mendix/web-widgets/e2e-spec"><img src="https://agentmods.dev/badge/commands/mendix/web-widgets/e2e-spec/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mendix/web-widgets/e2e-spec"><img src="https://agentmods.dev/badge/commands/mendix/web-widgets/e2e-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 714 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00714
Opus 5.5	$0.00000	$0.00286
Sonnet 5.5	$0.00000	$0.00143
Haiku 4.5	$0.00000	$0.00071

Measured 1mo ago against content hash 48c819b88e56, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

e2e-spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/mendix/e2e-spec.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are helping the developer write or improve Playwright e2e specs for a Mendix pluggable widget in the web-widgets monorepo.

Read first: docs/requirements/e2e-test-guidelines.md — owns all rules for imports, assertions, locators, navigation, and snapshots. Do not duplicate them here.

Context

Specs live at: packages/pluggableWidgets/<widget>/e2e/*.spec.js
Playwright strict mode is ON

<widget> throughout this document is the package folder name, e.g. badge-web, datagrid-web.

Before writing selectors, look up the actual widget names and menu labels in the .mpr:

# Full overview: modules, pages, entities, navigation menu labels
bash automation/mxcli/mx-testproject.sh inspect badge-web   # replace with actual widget name

# Widget structure of a specific page (reveals .mx-name-* values)
bash automation/mxcli/mx-testproject.sh exec <widget> "DESCRIBE PAGE <Module>.<PageName>"

# List pages if you don't know the page name
bash automation/mxcli/mx-testproject.sh list-pages <widget>

# Search for a widget name across all project strings
bash automation/mxcli/mx-testproject.sh search <widget> 'keyword'

The inspect output includes DESCRIBE NAVIGATION Responsive at the end — use those exact strings in page.getByRole("menuitem", { name: "..." }).

Spec file split

Standard naming convention per widget:

<widget>.spec.js — core rendering and data binding
onClick.spec.js — microflow, nanoflow, keyboard accessibility
dataTypes.spec.js — each supported Mendix attribute type
layouts.spec.js — widget inside list view, tab, data view, listen-to-grid

Running tests

# Full CI run (Docker):
pnpm --filter @mendix/badge-web run e2e   # replace with actual widget name

# Skip re-downloading the test project (useful when iterating locally):
pnpm --filter @mendix/<widget> run e2e --no-setup-project

# Skip re-downloading and rebuilding (fastest iteration; requires local test project files):
pnpm --filter @mendix/<widget> run e2e --no-setup-project --no-update-project

Read the full file on GitHub · 66 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 66 lines · 0 tokens per session scan A 48c819b88e56

Subscribe to this mod's changes

e2e-spec is a command published in the GitHub repository mendix/web-widgets (40 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 714 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Browser automation E2E testing Testing low-code mendix web-widgets

test

Run the app's microflow tests and verify it in the browser.

mendixlabs/mxcli · 13 tokens

mx-test-page

Drive Playwright against the testbed (port 8082). MANDATORY testbed-fingerprint guard (URL :8082 + "Test Project" ribbon) before any other assertion -- safety gate against driving the live project.

jordnlvr/MendixToolkit · 46 tokens

expect

Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…

yonatangross/orchestkit · 73 tokens

web-widgets: Command for Claude Code