Testing and UAT
Testing shows that the configured system runs the client’s processes from end to end. The agent writes and runs the system tests. The client’s testers run UAT through a shared form.
Write and run system tests
Section titled “Write and run system tests”- Ask the agent to write test scripts per process from the requirements and the design. It saves them as an artifact in the project.
- Ask the agent to run them in the sandbox. It creates test transactions and records the result of each script.
Test transactions are writes, so the agent asks for permission before the first one. Run system tests only in the sandbox or a test company.
Run UAT with the client
Section titled “Run UAT with the client”- Ask the agent for a UAT tracker form.
- Share it with the client’s testers through a link. Their answers are visible to your team as they type.
- Ask the agent to add each defect as a project task that names the requirement and the setting it affects.
- Ask for a sign-off form when the client signs off UAT.
What you decide
Section titled “What you decide”- Which processes go through UAT
- Who tests them
- Which defects block go-live
After UAT sign-off, continue with the production load and the cutover.