diff --git a/docs/img/reviews/Screenshot 2019-10-17 at 02.38.37.png b/docs/img/reviews/Screenshot 2019-10-17 at 02.38.37.png deleted file mode 100644 index d5db13fb..00000000 Binary files a/docs/img/reviews/Screenshot 2019-10-17 at 02.38.37.png and /dev/null differ diff --git a/docs/img/reviews/Screenshot 2019-10-17 at 02.43.31.png b/docs/img/reviews/Screenshot 2019-10-17 at 02.43.31.png new file mode 100644 index 00000000..795ad6cc Binary files /dev/null and b/docs/img/reviews/Screenshot 2019-10-17 at 02.43.31.png differ diff --git a/docs/reviews.md b/docs/reviews.md index e18dd12e..ba7dcf49 100644 --- a/docs/reviews.md +++ b/docs/reviews.md @@ -2,16 +2,16 @@ ## Context -Only bonus exercises can be reviewed, which are the last items of a quest. -Bonus exercises are available in quests 02 / 03 / 04 / 05 /07 / 08 / 09. -Screenshot 2019-10-17 at 02.38.37 +Only unblocked bonus exercises can be reviewed, which are the last items of a quest. +Bonus exercises are available in quests 02 / 03 / 04 / 05 / 07 / 08 / 09. +Screenshot 2019-10-17 at 02.43.31 Making a review involves 2 students who are gonna review each other's exercise. Each user has to : -- check the code of the other one on Github -- bet if it's gonna fail or succeed in the Review interface -- run his own exercise in the Review interface to give a result to compare with the bet, and state if it was right or wrong +- **check** the code of the other one on Github +- **bet** if it's gonna fail or succeed in the Review interface +- **run** his own exercise in the Review interface to give a result to compare with the bet, and state if it was right or wrong ## Usage @@ -30,7 +30,7 @@ Once you and the other student have confirmed the match, you can go and check th When you've checked his code, those 4 steps will have to be completed to achieve the review : - You have to bet if the exercise of the other student will fail or succeed after running the tester -- The other student has to do the same with your exercise and make his own bet, that you can see on the component `Review of your exercise` +- The other student has to do the same with your exercise and make his own bet, that you will see on the component `Review of your exercise` Screenshot 2019-10-17 at 02.20.18 - Once the other student's bet is set, the tester button unblocks and you have to run it on your exercise to output the result determining if your exercise has failed or succeeded ; this result is compared to the other student's bet to determine if it was wrong or right @@ -42,7 +42,9 @@ In fact, a bet is succeeded if it's equal as the tester output : You can have those 4 cases : -- You bet that the exercise will **fail**, the tester output states that the exercise has **failed** -> the bet is **succeeded** -- You bet that the exercise will **succeed**, the tester output states that the exercise has **succeeded** -> the bet is **succeeded** -- You bet that the exercise will **fail**, the tester output states that the exercise has **succeeded** -> the bet is **failed** -- You bet that the exercise will **succeed**, the tester output states that the exercise has **failed** -> the bet is **failed** +| bet | tester output | bet result | +| ------- | ------------- | ------------- | +| fail | failed | **succeeded** | +| fail | succeeded | **failed** | +| succeed | succeeded | **succeeded** | +| succeed | failed | **failed** |