Documentation that matches the app
Generated from the model rather than written by hand afterwards.
For Mendix developers
MendixWright
AI-generated Playwright end-to-end tests for Mendix — written from your app’s model, traced back to every requirement, and run from VS Code beside Studio Pro.
At a glance
From a Mendix app to a testable E2E suite
Select any part of the diagram to see what happens at that stage.
Choose a numbered area on the diagram, or a stage above, to explore it.
Your application model
Mendix Studio Pro
Start your app in Studio Pro as usual. MendixWright reads the compiled model — pages, navigation, domain model, microflows and integrations — so nothing has to be described by hand.
AI documentation & process discovery
Maia for Mendix
The model becomes a structured Business Requirements Document: overview, scope, user stories, functional and non-functional requirements, and open questions. Anything the model can’t tell us is marked to be confirmed rather than guessed.
Intelligent test generation
Playwright MCP
Playwright MCP connects to your running app to discover elements, selectors and dynamic behaviour in real time, then generates robust E2E tests with assertions tailored to your business logic.
Automated, reliable and repeatable
E2E Test Suite
The suite opens in VS Code’s Test Explorer, ready to run against your local build. Every Given/When/Then acceptance criterion links to the test that covers it, down to the file and line.
What you have at the end
Deliverables
Application documentation with user stories and journeys, an automated E2E suite, and test coverage and insights — plus a timestamped BRD for every run, so each release has its own record.
Six steps, end to end
The process
Ingest your documentation, understand the user journeys, discover the running app, generate the tests, execute them against your build, then maintain and evolve the suite as the app changes.
Faster, higher quality, built to scale
Why it matters
Faster time to value, higher quality releases, context-aware tests, coverage that grows without a matching growth in manual effort, and living tests that QA, developers and business analysts can all read.
How it works
From running app to tested requirements
- 01
Detects your local Mendix app
Start your app in Studio Pro as usual. The MendixWright extension for VS Code finds it straight away and shows the URL, Mendix version, admin port and health status. There’s nothing to configure.
- 02
Writes the BRD from the compiled model
MendixWright reads the app’s pages, navigation, domain model, microflows and integrations. From these it writes a structured Business Requirements Document: overview, scope, user stories, functional and non-functional requirements, and open questions. Anything the model can’t tell us, such as business value or priority, is marked to be confirmed rather than guessed.
- 03
Writes acceptance criteria you can test
Each user story gets Given/When/Then acceptance criteria. Each criterion links to the exact Playwright test that covers it, down to the file and line.
- 04
Generates and runs Playwright tests
The regression suite opens in VS Code’s Test Explorer, ready to run against your local build while you develop. That includes checks on live data from external APIs.
- 05
Keeps a versioned record of every release
Each run saves a timestamped BRD. That gives you a record of every version of the app for side-by-side testing, change tracking and release notes.
Why it matters
Requirements, tests and docs that stay in step
Regression coverage from day one
Without hand-scripting each test.
End-to-end traceability
From requirement to acceptance criterion to test.
Built for Mendix developers
Working in VS Code beside Studio Pro.
See MendixWright on your app
We’ll walk through a generated BRD and test suite on a real Mendix project.
Book a demo