ERP Testing Command Centre

SI-led Client-led Joint Client + SI Click any level for detail

PARALLEL NFT — Non-Functional Test Performance · Load · Security · DR · Batch · Resilience

Click a level to see detail

Each card shows who executes, who signs off, entry / exit criteria, deliverables, and the most common pitfall.

SI side

SI Test Lead

Manages SAT and SIT execution; co-authors test strategy with Client Test Manager; signs off SAT.

SI Test Team / SI Tester

Executes FAT (per sprint) and SAT scripts. On smaller programmes can be a sub-team within SI Functional Leads.

SI Functional Leads

Support FAT/SAT/SIT/UAT — clarify functional behaviour, triage functional defects, reproduce issues during UAT.

SI Technical Lead

Resolves technical and integration defects. Signs off Unit testing.

SI Solution Architect

Signs off SIT (architecture-level integrations) and NFT (non-functional requirements) jointly with client counterpart.

SI Programme Director

Programme-level accountability for delivery quality.

Client side

Client Test Manager

Owns test strategy from Client side; runs SIT; coordinates UAT/BAT; manages defect process; authors Pre-UAT scripts with Process Owners.

Process Owners

Accept FAT at sprint review; coordinate Pre-UAT/UAT (write scripts, manage coverage); sign off UAT per workstream; review BAT results. They do NOT execute UAT.

Users / End Users

Execute UAT scripts hands-on. Provide usability feedback. Actual business representatives who will use the system day-to-day.

Benefit Owners

Sign off Mini-BAT and BAT against the benefits map. Authority for business-readiness.

Solution Architect (Client)

Co-signs architecture decisions; signs off SIT with the SI counterpart.

IT Ops Lead

Executes / signs off NFT — performance, security, DR, batch.

Exec Sponsor

Authorises handover to Deploy phase based on evidence from all test levels.

FAT vs UAT — the most commonly confused boundary

The line is field-level vs process-level. Get this wrong and your acceptance evidence doesn't reflect real user experience.

FAT — Functional Acceptance Test

Field-level / configuration-level. Tests that individual user stories or configurations work as designed.

"The system allows creation of a case record with fields X, Y, Z. Confirm field types and validation."

Executed by: SI Tester · Accepted by: Process Owner at sprint review

UAT — User Acceptance Test

Process-level / business-flow. Tests end-to-end business journeys.

"A client advisor opens a case, captures contact details, progresses through the case journey to closure."

Executed by: Users (end users) · Signed off by: Client Test Manager + Process Owners

Quick test

If a tester is checking field X accepts data type A → that's FAT.
If a tester is walking through "I'm a stock controller, show me my Tuesday morning workflow" → that's UAT.

P1 — Critical

System unusable, no workaround

Blocks all testing or renders the area untestable. Ship-stopper.

ResponseImmediate

Resolution target24 hrs

Go-live toleranceZero open

P2 — High

Major function impaired, workaround exists

Important function broken but business can continue with manual or alternative steps.

Response4 hrs

Resolution target3 working days

Go-live toleranceZero or formally accepted

P3 — Medium

Minor function impaired, acceptable workaround

Inconvenience but not blocking. Logged with post-go-live fix plan.

Response1 working day

Resolution targetNext sprint

Go-live tolerance≤ 10 (FAT exit)

P4 — Low

Cosmetic or minor

Typos, alignment, label inconsistencies. Backlog candidates.

ResponseNext planning

Resolution targetBacklog

Go-live tolerance≤ 15 (FAT exit)

Defect lifecycle

Raised

→

Classified

→

Assigned

→

Resolved

→

Retested

→

Closed

/

Reopened

Go-live rule: zero P1; zero P2 unless a workaround is agreed and documented; P3 within published ceiling, with post-go-live fix plan; P4 in backlog. P2 workarounds must be agreed by the Design Authority and Process Owner and recorded in the Test Exit Report — no grey area.

Common pitfalls — call these out the moment you see them

Go-live gate checklist

Tick items as evidence is in. The sponsor signs the final authorisation only when all are green.

Readiness

0%

Not ready

Start with the test-completion sign-offs (FAT, SAT, SIT, UAT, BAT). Each is non-negotiable.

Level Finder

Describe what's being tested and who's doing it. The finder maps it to the right level.

Type a description above. Try phrases like: "checking field validation", "load test 5000 concurrent users", "end-to-end order to cash with 3rd party", "process owner running through case creation in sprint review".