Which variances should be explained in the Test Summary Report?

The variances that should be explained in the Test Summary Report primarily focus on differences between what was originally planned for testing and what was actually executed. This distinction is essential because it provides stakeholders with insights into the testing process's effectiveness and efficiency. By highlighting any discrepancies, the report can inform decisions about resource allocation, project timelines, and potential risk areas.

Addressing the variance between planned testing and actual execution allows teams to identify whether they faced unexpected challenges, scope changes, or other issues that impacted test coverage. It's crucial for ensuring that the testing aligns with the project goals and that any shortfalls or overachievements are documented and understood.

Other variances may also be relevant, such as those relating to defect counts or test case execution rates, but the core focus on the planned versus actual testing captures the overall alignment with project expectations and gives a comprehensive view of how effectively the testing objectives were met.