Monitor ERP.

The Situation

Monitor had an established manufacturing ERP — a product with years of development behind it, used by real customers who knew how it worked. They were building a web client to match it: a browser-based version that had to behave identically to the Windows application, page by page, scenario by scenario.

The codebase was complex, the scope was large, and the existing team needed additional capacity. What they were building couldn't afford to drift from the original — existing customers would migrate to it, and any gap between what they expected and what they got would be a problem.

The Constraint

Indpro started with frontend development and bug fixes alongside Monitor's team. Early on, it became clear that contributing to a codebase without backend access — where every change required extended coordination — limited what the team could actually deliver.

What We Did

The decision was made to restructure the engagement around test ownership. Indpro took full responsibility for writing Playwright tests and managing the nightly pipeline that runs them.

The team documents workflow scenarios across the entire application, flags feature regressions before they become release problems, and reports gaps in development to Monitor's team as they surface.

The shift mattered because it created a clear boundary of ownership. Instead of contributing to a shared codebase in a constrained way, Indpro owned a complete function — one that produced visible, measurable output and reduced the communication overhead on Monitor's side significantly.

Key Deliverables

• Scenario mapping — Every workflow in the application documented and structured into testable scenarios, building coverage from the user's perspective
• Regression detection — A nightly pipeline surfaces any regression introduced in the previous day's development, before it reaches a demo or release
• Reusable architecture — The test structure and methods built by Indpro are now the blueprint for how future features will be tested

The Result

Monitor now has a nightly pipeline that runs every morning and surfaces any regression introduced the previous day. Issues that would previously go undetected until a demo or release are caught in the development cycle — where fixing them costs hours, not weeks.

Impact

• 150+ workflow tests written in approximately 3 months
• 370+ page-load tests covering every page in the application
• 33% of total test coverage built in a fraction of the time

The test architecture and reusable methods Indpro built are now the blueprint for how future features will be tested. The output of this engagement doesn't end when the engagement does.

"The ticket generation and test writing helps identify issues that go unnoticed during development. Our tests help a lot to identify feature flaws."

— Christer Andersson, Team Manager, Monitor