The testing step is where the rubber meets the road! Each team presents their proposed solution to a large public audience, which may include outside experts, administrative decision makers (who may have already participated in the process), and other community members. The audience participates in assessing the solution, providing formal feedback to the team. This feedback serves as further formative assessment.
Based on feedback, the team may need to return to the implementation step to further revise their solution. Testing is therefore another iterative step and time must be allocated for at least one revision cycle.
During project testing, a minimum of these HQPBL principles are being practiced: intellectual challenge and accomplishment; authenticity; public product; and collaboration.