Redaguoti

Bendrinti naudojant

Checklist for your test strategy

  • Straipsnis

Planning

Done? Task
✓ Plan how you'll create, run, and manage your test cases. Estimate how many resources (people, hardware, environments, devices) you'll need for each test cycle. Align your test cycles with the processes that are in scope for your project.
✓ Set up a tracking system that monitors the progress, results, ownership, and issues of each test case. Define a process for fixing, retesting, and deploying corrections for any errors that you find during testing.

Implementation

Done? Task
✓ Make sure your developers do unit testing in a development environment. Unit testing checks the function, code, and configuration of all extensions and integrations that you add to your solution.
✓ Make sure your functional consultants or subject matter experts (SMEs) do functional testing in a test or development environment. Functional testing validates the design of your solution against the requirements.
✓ Make sure your SMEs do process testing in a test environment. Process testing runs multiple processes consecutively and checks whether your solution supports your business operations. It also looks for any unintended outcomes or side effects.
✓ Do performance testing on critical processes throughout the Implement and Prepare phases. Performance testing measures how well your solution performs under realistic load and growth conditions.
✓ Do end-to-end testing throughout the Implement and Prepare phases in a test environment. End-to-end testing covers all the full business processes in scope and all the connected integrations and solutions. Use increasingly realistic migrated data for each test cycle.
✓ Do user acceptance testing (UAT) in a test environment during the Prepare phase. UAT tests how ready your users, processes, and solution are to operate the business in the new environment.
✓ Do regression testing in a test environment, or in a development environment for updates, throughout the Implement and Prepare phases and after go-live. Regression testing makes sure that the solution performs as expected after a change.
✓ Consider using automation for functional, process, end-to-end, performance, and regression testing. Automation can save you time and effort by running repetitive or complex tests faster and more accurately.
✓ Create a test communication plan with clear scope and objectives. Specify the schedule, sequence, roles, and issue resolution process for each test cycle. Communicate the plan to all the stakeholders and participants involved in testing.

Go-live

Done? Task
✓ Plan a mock cutover in the new production environment. A mock cutover tests and confirms the estimated time and steps for all the tasks that you need to do during the go-live stage.

Next steps