Verifying before go-live.
WHAT TO TEST
Every process, end to end Every integration Every report Every role's permissions Period-end procedures
WHY PERIOD-END SPECIFICALLY
It is performed rarely, so problems are discovered at the worst time.
WHAT UNIT TESTING MEANS HERE
Individual functions working as configured.
WHAT INTEGRATION TESTING MEANS
Data flowing correctly between modules and systems.
WHAT USER ACCEPTANCE TESTING MEANS
Business users confirming the system supports their work.
WHO SHOULD PERFORM IT
The people who will use it.
WHY NOT the project team
They know the intended path, and will follow it.
WHAT TO TEST WITH
Real data, and real scenarios.
WHAT TO INCLUDE
Exceptions Corrections and reversals High-volume periods Interruptions
WHAT TO DOCUMENT
Every test, its result, and its resolution.
WHAT TO DEFINE
What must pass before go-live.
WHAT TO NEVER DO
Reduce testing because of the timeline.
WHY
Every problem not found in testing is found by users, in production, at greater cost.
WHAT TO TEST LAST
The full process, by users, unassisted.
