Testing during project implementation ensures that business processes are verified and validated as initially agreed upon during the design phase. Establishing a clear test strategy is a critical component of the project plan.
Three key focal points when preparing for testing phases are described below:
WHO Will Be Testing?
A test management team will oversee the process in collaboration with project management to define the testing scope. Testers should include participants from the design phase, as well as business experts and end users.
WHAT Will Be Tested?
Identify in advance which business scenarios, master data, and transactional data are relevant for testing. Key areas include:
- Roles, permissions, and authorizations.
- Business elements such as countries, regions, products, customers, and locations.
- Specific scenarios that require targeted data.
WHERE Will Testing Be Performed?
Select the appropriate testing environment, whether it’s Development (DEV), Quality (QA), or a production-like environment (PROD).
HOW Will Testing and Issues Be Managed?
The test manager will assign test plans with specific test packages and communicate schedules. A structured approach to issues reporting is essential, using a tool to document issues or needed changes, including details such as the tester assigned, issues owner, and resolution priority.
WHEN Will Testing Occur?
Testing phases should have clear timelines in the project plan, typically starting during the realization phase after the design review is completed. Different teams in the project will conduct various types of testing:
- The implementation team handles unit and integration testing.
- Business users are responsible for User Acceptance Testing (UAT).
Note
