Zeyto Academy · Advanced · Module 25
Testing, training and go-live
Plan and run testing and UAT, train end users, execute the cutover, support hypercare, hand over to support, close the project and measure success.
You will be able to
- Write a test plan, scripts and scenarios with ledger checks, negative cases and role tests
- Run UAT with key users, triage defects and obtain sign-off
- Build a role-based training plan using Zeyto's help and training database
- Prepare a cutover plan, go-live checklist and go/no-go criteria
- Run go-live, hypercare and stabilisation
- Hand over to support, close the project and measure success against baselines
Test planning
- Test by layers: configuration, process, integration, migration, roles, output, backup and UAT.
- Every requirement needs a script; every script an expected result.
- Severity decides what must be fixed before go-live.
Writing test scripts and scenarios
- A script has preconditions, numbered steps, specific expected results and a ledger check.
- Test negative cases, corrections and roles, not only the happy path.
- Write the expected figures first.
User acceptance testing and sign-off
- The client's key users execute UAT; the consultant supports.
- Triage daily and retest fixes with a few related scripts.
- Sign-off records the known state, including accepted open items.
End-user training
- Train by role, close to go-live, with real examples.
- Use in-product help, Ctrl+K and a training database; help is English only.
- Check competence with a signed task checklist, not just attendance.
The cutover plan and checklist
- The cutover plan is built from rehearsals, with an owner and time for every task.
- Remove test data, set Live mode, activate the licence, post openings and test the backup.
- Go/no-go uses stated criteria, not feelings.
Go-live day, hypercare and stabilisation
- Be on site, visible and logging every issue on go-live day.
- Triage tickets as bug, configuration, training or change request.
- Stability means falling tickets, no severe defects, a closed month-end and tested backups.
Handover, project closure and measuring success
- Hand over a complete pack, and show the client's administrator the support and recovery tools.
- Close the project with acceptance, final invoice, lessons learned and archive.
- Measure benefits against baselines agreed before the project.
Test planning: key table
| Test type | What it proves | Who tests |
|---|---|---|
| Configuration test | Each setting is as the workbook says | Consultant |
| Process test | A single process works from start to finish, such as quotation to receipt | Consultant, then key users |
| Integration (end-to-end) | Processes connect: a sale reduces stock, creates the receivable and VAT, and reaches the reports | Consultant and accountant |
| Data migration test | Loaded balances reconcile to the old system | Accountant and consultant |
| Role and security test | Each role sees and can do only what it should | Consultant and process owners |
| Output test | Prints, PDFs, exports and labels look right on the real printers | Key users |
| Backup and restore test | A backup can be restored | Technical consultant |
| User acceptance test (UAT) | The business accepts the system | Client key users |
Test planning: key table
| Severity | Meaning | Example | Response |
|---|---|---|---|
| 1 Blocker | Cannot work or amounts wrong | An invoice cannot be submitted, or VAT posts to the wrong box | Fix before go-live |
| 2 Major | Important function fails, workaround exists | Print layout cuts off the total | Fix before go-live unless agreed |
| 3 Minor | Small problem | Label wording | Fix in hypercare |
| 4 Cosmetic | Appearance only | Spacing | Backlog |
Writing test scripts and scenarios: key table
| Field | Content |
|---|---|
| ID and title | TS-OTC-01, Cash-on-credit sale with VAT |
| Requirement ID | R-02 |
| Preconditions | Customer C001 credit limit AED 20,000; item I-100 price AED 100, cost AED 60, stock 50; user with Sales role |
| Steps | Numbered, one action each |
| Expected result | Specific figures and screens |
| Ledger check | What Posting Trail and reports must show |
| Result and tester | Pass or Fail, name, date, defect ID |
Writing test scripts and scenarios: key table
| Process | Scenario | Priority |
|---|---|---|
| Sales | Quotation to order to delivery note to invoice to receipt | Must |
| Sales | Credit limit exceeded | Must |
| Sales | Return with credit note | Must |
| Purchase | PO to GRN to purchase invoice to payment | Must |
| Stock | Transfer between warehouses and an adjustment | Should |
| POS | Cash sale, card sale, shift close | Must for retail |
| Finance | Receipt allocation to oldest invoices; PDC deposit and clearance | Must |
| VAT | Return Worksheet equals reports | Must |
| Roles | Each role's allowed and refused actions | Must |
User acceptance testing and sign-off: key table
| Day | Focus | People |
|---|---|---|
| 1 | Briefing, access check, sales scripts | Sales manager, reps, accountant |
| 2 | Purchase and stock scripts | Purchasing manager, storekeepers |
| 3 | Finance, VAT, bank and role tests | Accountant, finance manager |
| 4 | Free-play with real examples, outputs and printing | All key users |
| 5 | Retest of fixes, results review, sign-off meeting | Sponsor and process owners |