How to choose the right testing strategy?

Required tools

• Azure DevOps — Test Plans document the testing tasks that follow from the strategy.
• Test policy template — The template in which the selected test strategy and quality requirements are documented.

Know the three strategies

1. 1.Use specification-based testing as a general rule

   Test against the customer's requirements in user stories and acceptance criteria without knowing how the system works under the hood (black box). This is ProsessPilotene's preferred strategy, and the one the customer normally uses for their own testing.

2. 2.Use structure-based testing for custom-developed code

   Testing with full insight into the solution (white-box testing) for integrations and custom software outside Dynamics 365 — this is normally ProsessPilotenes responsibility.

3. 3.Use experience-based testing as a supplement

   Have an experienced tester anticipate potential weaknesses in the solution and investigate them, as a supplement to the other strategies.

Choose a strategy based on delivery type

1. 4.Align the strategy with the delivery

   Choose specification-based testing for requirements and user stories, structure-based testing for integrations and custom-developed code, and experience-based testing as a supplement where relevant.

2. 5.Document the choice in the test policy

   Document the selected testing strategy in the test policy, along with the division of responsibilities between the customer and the supplier—this affects all project estimates.

3. 6.Aim for automated testing

   Enable as much of the testing as possible to be performed by machines, with the goal of having 80% of deliverables tested automatically.