What is edit-test-project?

Instructions for editing a Mendix test project stored in an .mpr file so it can support a Playwright end-to-end test. Mendix is a low-code development platform, and end-to-end tests check a complete user flow in a running application.

Use them to update widget test projects, prepare mxcli, create backups, and support new or changed Playwright browser tests.

They provide the required preparation and backup steps for safely changing a project file that must be closed in Mendix Studio Pro.

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/edit-test-project.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/edit-test-project/github.svg)](https://agentmods.dev/commands/mendix/web-widgets/edit-test-project)

Your own site

<a href="https://agentmods.dev/commands/mendix/web-widgets/edit-test-project"><img src="https://agentmods.dev/badge/commands/mendix/web-widgets/edit-test-project/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/edit-test-project"><img src="https://agentmods.dev/badge/commands/mendix/web-widgets/edit-test-project.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 2,218 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.02218
Opus 5.5	$0.00000	$0.00887
Sonnet 5.5	$0.00000	$0.00444
Haiku 4.5	$0.00000	$0.00222

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

Security

Grade A, and why

edit-test-project 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/edit-test-project.md · 190 lines

How it starts

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

You are helping the developer edit a Mendix test project (.mpr file) to support a new or updated Playwright e2e test in the web-widgets monorepo.

Context

Test projects live at: packages/pluggableWidgets/<widget>/tests/testProject/<Name>.mpr
mxcli reads/writes .mpr files via MDL (Mendix Definition Language)
Binary: automation/tools/mxcli — gitignored, install with bash automation/mxcli/setup.sh
The .mpr must be closed in Studio Pro before mxcli can edit it
mxcli is alpha software — ensure .mendix-cache/backup/AppBackup.mpr exists before bulk edits
For Playwright rules that new pages must satisfy, see mendix:e2e-spec and docs/requirements/e2e-test-guidelines.md

Ask the user (or infer from context): which widget, and what scenario requires a test project change?

Step 2 — Check prerequisites

[[ -x automation/tools/mxcli ]] && echo "OK" || bash automation/mxcli/setup.sh
ls packages/pluggableWidgets/<widget>/tests/testProject/*.mpr | grep -v backup

Verify Studio Pro is not holding the project open before any mxcli writes:

ls packages/pluggableWidgets/<widget>/tests/testProject/.mendix-cache/lock 2>/dev/null \
  && echo "⚠️ Studio Pro lock file present — close the project first" \
  || echo "OK — no lock file"

Step 3 — Inspect current state

# Full overview: modules, pages, entities, navigation
bash automation/mxcli/mx-testproject.sh inspect <widget>

# Targeted queries:
automation/tools/mxcli -p <MPR_PATH> -c "SHOW PAGES IN <Module>"
automation/tools/mxcli -p <MPR_PATH> -c "SHOW ENTITIES IN <Module>"
automation/tools/mxcli -p <MPR_PATH> -c "SHOW MICROFLOWS IN <Module>"
automation/tools/mxcli -p <MPR_PATH> -c "DESCRIBE PAGE <Module>.<PageName>"
bash automation/mxcli/mx-testproject.sh search <widget> 'keyword'

DESCRIBE PAGE caveat: pages containing only pluggable widgets (no built-in widgets like DATAVIEW, LAYOUTGRID, etc.) may render as an empty body even when widget content exists in the MPR. Use automation/tools/mxcli bson dump -p <MPR> --type page --object <Module>.<Page> and grep for widget names to verify content was written.

Read the full file on GitHub · 190 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 · 190 lines · 0 tokens per session scan A 471a19bce873

Subscribe to this mod's changes

edit-test-project 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 2,218 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