This guide highlights the process for signing up for a code review of the homework. This is relevant for the Homework v1.2 Review, Homework v3.2 Review, and Homework v4.2 Review assignments.
TABLE OF CONTENTS
Code review is only performed on functional and cleaned up code. See below for details.
The autograder bot will verify the eligibility of your code for review by checking the following:
Your code must pass all of the relevant homework tests.
For example, for Homework v1.2 Review, your code must still pass the tests for Homework v1.0 Tests and Homework v1.1 Tests assignments.
Your code must not have any compile or Javadoc warnings.
Your code must not have any TODO comments remaining. When you are done with a TODO comment, go ahead and delete it. There is no need to keep those comments around in the code.
Your code must be free of stack traces. While these are useful for debugging, your code should decide how to deal with an exception before code review.
The autograder bot will notify you if there are any of the above style issues. Go to the GitHub Action run logs to find the exact issue and line number. Otherwise, it will indicate the code passed the automated checks required for a code review.
If you see a message like:
► Check for ???…. ❌ Unable to ???. Expand above for details.
You need to open the “Check for” toggle above the error message to see the exact issues.
For example: