Skip to content
Tutorials Center
My learning

Topics

Lesson 23 of 36 ยท Implementation and Change

Testing, Cutover and Go-Live

Plan ERP and CRM testing layers, user acceptance, defect handling, cutover runbooks, go/no-go decisions and hypercare, with Python tools for defects and a cutover timeline.

The last stretch of a project decides whether the business keeps running. Testing shows that the system does what the business needs; the cutover moves the company from the old system to the new one; the go-live decision says "now". All three need discipline because the cost of an error rises sharply once real customers, invoices and stock movements are involved.

The product is not available on this site, so the techniques are modelled with Python stand-ins: a defect tracker, a test coverage report and a cutover timeline.

Layers of testing

Build-time tests

Unit test One setting or one function.
Integration test A full flow across modules and systems.

Run by the project team, early and often.

1 / 3
  • Unit tests check one configuration, validation rule, workflow step or report.
  • Integration (end-to-end) tests follow a business scenario through every step and system: create a quotation, convert it to an order, check credit, deliver, invoice, receive payment, and check the ledger. Test interfaces with realistic messages, including errors.
  • Performance tests run expected peak volumes, such as month-end posting or a big import, and check response times.
  • Security and role tests confirm that each role sees only what it should and that segregation of duties holds (for example, nobody can both create and approve a payment).
  • Regression tests repeat earlier tests after changes, ideally automated for stable flows.
  • User acceptance testing (UAT) uses real business users, written scripts based on their processes, and realistic data. Sign-off means "this system supports our work."

Test cases and traceability

Each test case has an ID, the requirement it proves, preconditions, steps, expected results, the actual result and a status. Traceability links requirements to test cases so you can show that every Must requirement has at least one passed test.

Python Requirement coverage report (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Defect management

Every problem found goes into a defect log with a severity and a status. Typical severities:

Severity Meaning Example
1 Critical Business stops or data corrupts, no workaround Invoices post to the wrong ledger account
2 High Major function broken, workaround is hard Approval workflow does not start
3 Medium Function impaired, workaround exists Report totals need manual refresh
4 Low Cosmetic Label spelling

Go-live criteria commonly demand zero open severity-1 and severity-2 defects, and a plan with owners for the rest.

Python Defect log and go-live criteria

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The cutover plan

Cutover is the controlled sequence of steps that stops the old system, moves data and brings the new system live. It is written as a runbook: a time-ordered list of tasks, each with an owner, a duration, dependencies and a verification step. Typical elements:

  1. Freeze: stop changes in the old system (no new master data, last order cut-off).
  2. Final extraction: export open items (open orders, open invoices, stock balances, customer balances).
  3. Load and reconcile: load into the new system and check that totals match, such as stock quantity and value and the trial balance.
  4. Smoke tests: run a few critical transactions in production.
  5. Go/no-go checkpoint: the steering committee decides to open the system, or to roll back.
  6. Open to users and announce.

Plan for a rollback: the exact conditions that trigger it, who decides, and how to restore the old system. The point of no return should be as late as possible. Rehearse the whole sequence at least twice in a production-like environment to measure the real duration of each step.

Python Cutover timeline with a time window

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Rehearsals typically show that loads take longer than planned. A buffer of 20 to 30 percent of the window is a common rule of thumb.

The go/no-go decision

The steering committee reviews a checklist: test sign-off, open defects, data reconciliation, trained users, support ready, rollback tested, business readiness (for example stock count done, customers informed). The rule that saves projects is simple: a no-go is a legitimate result. Moving the date by two weeks is cheaper than a failed go-live.

Hypercare

After go-live, keep the project team on duty for hypercare: a war room or a dedicated chat, daily stand-ups, a fast defect-fix cycle, monitoring of interfaces and batch jobs, and extra attention to financial closes. Watch leading indicators: order backlog, unposted documents, integration errors, help-desk volume. When indicators return to normal, formally hand over to the regular support organization.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Who should perform user acceptance testing?

    UAT proves that the system supports the business, so it must be performed by the people who do the work.
  2. 2. What is a cutover rehearsal for?

    Rehearsals expose timing and sequencing problems while there is still time to fix them.
  3. 3. A severity-1 defect is still open on the go-live checklist. What is the usual decision?

    Severity-1 defects stop the business. Go-live criteria normally require none, and any exception is an explicit committee decision.
  4. 4. What does traceability give you?

    With traceability you can show that every Must requirement has passed at least one test.

Summary

  • Test in layers: unit, integration, performance, security, regression and UAT.
  • Trace requirements to tests and manage defects by severity with clear go-live criteria.
  • Write the cutover as a runbook, rehearse it, plan the rollback and keep a time buffer.
  • A no-go decision is cheaper than a failed go-live.
  • Hypercare watches indicators until operations are stable.

Next: Master Data Management