Testing the patch as part of the review process will ensure a stable merge. The page provides different options to ensure that patch is tested before merging.
- Testing by one or more reviewers. This option has been followed for long time in VSPERF. The reviewer(s) tests the patch in their testbed and share the outcome. Though this option simplifies many things, at times, it increases the workload on single reviewer.
- Testing on Public testbed, such as Intel Pod-12, by reviewer(s) and/or submitter. This option is similar to (1), but supports workload sharing. Setting up and testing in public-testbed helps in multiple reviewers and submitter sharing the workload of 'testing the patch'.
- Internal testing by the Submitter, followed by publishing of the test-details in Jira. This option is where the submitter of the patch itself shares the test results, including testcase(s), and corresponding configurations. The details should be included in the Jira issue description.
- LAST OPTION - Include comment "Not Tested During Review". This option is least preferred, and VSPERF will try its best to avoid this option.