What it is
Setting up a durable test stack and writing a structured user-acceptance-testing playbook: unit, integration, E2E, load, CI/CD.
For whom
Tech teams under shipping pressure with no tests, or clients needing a formal UAT plan before user acceptance.
Indicative price
Fixed price on quote, indicative EUR 6,000 to 20,000 excl. VAT. Team training + runbook included.
Acceptance is what protects your users, your revenue and your business team's credibility at deployment. It cannot be improvised at the last minute.
- 1
A test plan formalizes what the software must do, with precise scenarios, measurable acceptance criteria and realistic data sets. Without it, acceptance becomes a subjective exercise no one can arbitrate.
- 2
Acceptance is when the business validates, not engineering. The business owns the edge cases, regulatory exceptions and real usage — engineering cannot anticipate all of them.
- 3
A well-crafted test plan is reusable: version after version, it becomes a regression base and a quality repository the team capitalizes on over time.
- 4
The acceptance minutes are a defensible document. They bind the vendor, protect the buyer, and formally trigger go-live, invoicing and warranty.
Types of tests we cover
A complementary set of tests — acceptance is not just a series of clicks.
Manual functional tests
Step-by-step verification that each delivered feature does what was asked. Foundation of any acceptance.
User tests
Real end-users on real scenarios. We observe, note the frictions, adjust before general opening.
Acceptance execution
Guided execution of the plan with the sponsor. Each scenario is played, acceptance criteria validated, gaps recorded.
Exploratory tests
Free exploration by an experienced tester looking for failures where the plan doesn't go. Complements predefined scenarios usefully.
Regression tests
Replay, at each version, the base of already-validated scenarios to ensure changes did not break existing behavior.
User Acceptance Tests (UAT)
The final validation step by the sponsor before go-live. Official acceptance leading to signed minutes.
Load and performance tests
Check behavior under volume and concurrency close to target production. Identify thresholds.
Accessibility tests
Check conformance to accessibility standards (WCAG). Mandatory for public actors and increasingly expected elsewhere.
A modular engagement, from plan to training, based on your maturity level.
Test plan writing
Turnkey test plan: detailed scenarios, acceptance criteria, data sets, environments, prerequisites. Word or spreadsheet, reusable version after version.
Acceptance execution
We play the scenarios with your business team, log the gaps, write the defect reports, produce the execution report and signed acceptance minutes.
Business team training
Training your business team to design, execute and maintain test plans. Goal: make them autonomous on future versions.
Reusable repository
Setup of a versioned test repository, organized by module and version. Support in defining acceptance criteria from the specification stage.
Frequent questions
What must a test plan contain?+
At minimum: the list of scenarios (functional and edge cases), measurable acceptance criteria per scenario, data sets, target environments, prerequisites, each participant's role, traceability between scenario and requirement, and the defect grid.
Role of the business vs the tester?+
The business brings the knowledge of real cases, validates acceptance criteria, decides on acceptance or rejection. The tester structures, executes methodically, records gaps objectively, does not take sides. Both roles are essential and must stay distinct.
How much does it cost?+
Fixed-fee quote. Writing a plan for a standard module: 3 to 6 days. Executing an acceptance campaign: 3 to 10 days depending on volume. Business training: 1 to 2 days. Full repository + 3-month follow-up: 15 to 25 days. From €3,500 excl. VAT for a focused plan.
Do you only test software you built?+
No — most of our acceptance work is on software built by others. We are vendor-independent, which is precisely the point for defensible acceptance minutes.
Which deliverables are defensible against the vendor?+
The jointly validated test plan, the execution report with a timestamped list of scenarios played and their status, the recorded defect sheets, and the signed acceptance minutes that formally trigger go-live, warranty and final invoicing.
/ En résumé
An acceptance to prepare seriously?
Free 1-hour scoping. Test plan delivered in 5 to 10 business days depending on scope.
Continue with
Pages that pair well with this one
Adjacent topics covered by MAG&Cie, hand-curated to stay on your problem.