This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| test:review-shepherd [2013/07/31 16:59] – Documentation for the Shepherd review process workflow rhauck | test:review-shepherd [2013/07/31 17:25] – added workflow diagram rhauck | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| Whether using this process or Github, test authors and reviewers must adhere to the [[https:// | Whether using this process or Github, test authors and reviewers must adhere to the [[https:// | ||
| + | |||
| + | The general process looks like this: | ||
| + | |||
| + | {{: | ||
| ==== Process for New Tests ==== | ==== Process for New Tests ==== | ||
| Line 13: | Line 17: | ||
| - When a test author is ready for tests to be reviewed, s/he must push them to the repository in a directory named '' | - When a test author is ready for tests to be reviewed, s/he must push them to the repository in a directory named '' | ||
| - The test author should then ask for a review on the < | - The test author should then ask for a review on the < | ||
| - | - When a reviewer comes forward, s/he should examine the tests for correctness with respect to the [[https:// | + | - When a reviewer comes forward, s/he should examine the tests for correctness with respect to the [[https:// |
| - The reviewer should then notify the mailing list of the test review. It is not necessary to include all of the review feedback in the mail, just a link to the test suite in Shepherd. | - The reviewer should then notify the mailing list of the test review. It is not necessary to include all of the review feedback in the mail, just a link to the test suite in Shepherd. | ||
| - **If the test passes review:** Go to the next step. | - **If the test passes review:** Go to the next step. | ||
| Line 41: | Line 45: | ||
| * [[http:// | * [[http:// | ||
| * [[http:// | * [[http:// | ||
| - | |||