The verdict in three sentences
The test plan is the life insurance of your go-live: it turns "it seems to work" into measurable, traced acceptance criteria. Investing 10 to 15 % of the project budget in testing isn't an expense, it's coverage: a bug caught in production costs about ten times more than in UAT. The provisional acceptance and final acceptance warranty phases (30 to 90 days) frame defect correction after delivery.
The components of a test plan
A project manager who wants to secure go-live must formalize four building blocks, otherwise UAT becomes a series of random clicks.
| Component | Content | Why it's critical |
|---|---|---|
| Test scenarios | Nominal, edge and error cases | Covers real business usage |
| Data sets | Representative data, volume | Reveals load bugs |
| Acceptance criteria | Measurable success conditions | Triggers final payment |
| Tracking log | Defects, severity, status | Traces fix and retest |
Defects must be classified by severity (blocking, major, minor): only this hierarchy lets you decide whether you can go live or not.
The cost of a bug and the warranty phases
| Detection moment | Relative fix cost |
|---|---|
| In design/specs | x1 |
| In development | x2-3 |
| In UAT | x5 |
| In production | x10 and up |
After delivery, two contractual phases protect the client:
| Phase | Typical 2026 duration | Purpose |
|---|---|---|
| Provisional acceptance | 15-30 days | Functional UAT before go-live |
| Final acceptance | 30-90 days | Stability in real conditions |
| Corrective warranty | 3-12 months | Fixing residual defects |
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Tying final payment to provisional acceptance, and a retention to final acceptance, aligns the vendor's interests with quality.
Mini case study
Lucas, project manager at a mid-sized firm in Rennes, prepares the go-live of a field-service management app. The project costs 64,000 EUR. He allocates 12 %, or 7,700 EUR, to a formal test plan: 45 scenarios, realistic data sets, quantified acceptance criteria. UAT detects 9 defects including 2 blocking ones on intervention-time calculation. Fixed in UAT, they cost about 1,800 EUR of rework. In production, those same bugs would have hit the billing of dozens of clients: estimated cost with a x10 factor, on the order of 18,000 EUR between emergency fixes, credit notes and lost trust. The test plan thus protected about 16,000 EUR of risk for 7,700 EUR invested.
FAQ
How much should I budget for testing? Budget 10 to 15 % of the project for a business application, more if criticality is high (payroll, billing, health). It's risk coverage, not an optional add-on.
What's the difference between provisional and final acceptance? Provisional acceptance verifies the app works per spec before go-live; final acceptance verifies it stays stable in real use over 30 to 90 days. Final payment is usually tied to these milestones.
Who writes the test scenarios? Ideally the business side, since it knows the real use cases, with methodological support from the vendor. Scenarios written only by tech often miss business edge cases.
Why does a bug cost x10 in production? Because it adds urgency, impact on real users, corrupted data to fix and lost trust. Catching it early means fixing it calmly and for far less.
Should I hold a retention? Yes, a 5 to 10 % retention released after final acceptance encourages the vendor to fix residual defects quickly. It's a simple, standard quality lever in 2026.
Let's scope your project. Tell us about your application, its criticality and your go-live deadline: we'll frame a test plan and provisional/final acceptance milestones. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
