Week 11
Justin review:
Variable names, are they meaningful and clear?
Variable names are meaningful and clear
Logic that could be more efficient
Logic looks sound. Selects a random word for guessed word, which is a neat solution
Unused imports or warnings.
No unused imports, one one warning present
Clear formatting
Formatting is good. Just one small nitpick: add spaces before ‘(‘ and after ‘{‘ i.e. if(debug){-> if (debug) {
Are there comments?
All class methods have comments
Which unit tests pass?
All unit tests pass
Variable names, are they meaningful and clear?
Variable names are meaningful and clear. Just one small nitpick: Scanner sc → Scanner scanner
Logic that could be more efficient
Logic looks sound. Only improvement I can think of is selecting a random word for the guessed word, as presented by Justin’s code
Unused imports or warnings.
No unused imports, only one warning present
Clear formatting
Formatting is good. Just one small nitpick: add space after ‘)’ i.e. public int exit(){ → public int exit() {
Are there comments?
All class methods have comments placed above + additional comments placed within method
Which unit tests pass?
All unit tests pass
- Logic is clear, unit tests pass, some issues with formatting.
- Everyone's code was sound, although I did see one warning that was present in everyone's code, but it was probably not a problem.
- What improvements would you make to your code/what was suggested?
- I would make sure the formatting of my output was clearer
- Which unit tests were the hardest to pass?
- I think checkLose() was the hardest one to pass since one of my indexes were off by one.
- How do the existing tests function and could they be improved?
- Do the existing unit tests cover the full range of the sub classes?
- The tests appear to cover most of the class methods
- How would you change the unit tests?
- Keep in mind I do not want them to change but this doesn't mean I think they are perfect. Reading through the tests is a good way to learn what the code should do thinking about how to test the codeis a good way to learn how to make tests.
- Maybe add more possible words to the test file to test against.
- What did you struggle with?
- Maybe getting some of the tests to pass
- What did one of your teammates struggle with?
- No clear struggles, appeared to go smoothly
- Was any part of the code a struggle for YOU?
- Set up one of my variable initializations incorrectly, although I spotted it after using the debugger.
- Was any part of writing the code easy for YOU?
- Yes, the getters/setters
- What was your biggest HW1 victory?
- Probably getting the unit tests to pass
Comments
Post a Comment