root
/
public
mirror of https://github.com/01-edu/public.git
14
27
Fork 0
Code Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
567 Commits
41 Branches
11 Tags
349 MiB
 
 
 
 
 
 
Tree: 46a251c9c1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '46a251c9c1'
${ noResults }
public/docs/reviews.md

3.0 KiB
Raw Blame History

Reviews

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

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

Usage

To submit an exercise to review and be reviewed, go to the Review panel on the right of the quest interface and click on the button to submit it :

Screenshot 2019-10-17 at 01.59.32

Then, when a match with another student who also wants to review is found, you'll be notified :

Screenshot 2019-10-17 at 02.03.11

Once you and the other student have confirmed the match, you can go and check the code of the other student on his repository in the component Your review :

Screenshot 2019-10-17 at 02.05.46

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 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

  • The other student also has to run the tester on his exercise to determine his result and so if your bet was wrong or right Screenshot 2019-10-17 at 02.22.30

In fact, a bet is succeeded if it's equal as the tester output : Screenshot 2019-10-17 at 02.24.04

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