artballesteros/cse15l-lab-reports

https://artballesteros.github.io/cse15l-lab-reports/

cse15l-lab-reports's Issues

Lab Report 4 Feedback

Here is your feedback for Lab Report 4:

• Provides link to their markdown-parse repository
• Provides link to the markdown-parse repository they reviewed

Snippet 1

• Shows the test(s) / expected output in MarkdownParseTest.java
• Shows the output of running test(s) for their implementation
• Shows the output of running for the implementation they reviewed
• Answers the code change question about their program

Snippet 2

• Shows the test(s) / expected output in MarkdownParseTest.java
• Shows the output of running test(s) for their implementation
• Shows the output of running for the implementation they reviewed
• Answers the code change question about their program

Snippet 3

• Shows the test(s) / expected output in MarkdownParseTest.java
• Shows the output of running test(s) for their implementation
• Shows the output of running for the implementation they reviewed
• Answers the code change question about their program

Additional comments from your grader:

Feel free to comment below any questions about the rubric/feedback

---

If you don't have all the checkmarks above, fix the issues described, and then submit a regrade request on Gradescope. Use this template for your regrade request:

• Link to this issue
• Link to your published lab report page

Lab Report 1 Feedback

Here is your feedback for Lab Report 1:

• All relevant URLs written as markdown links
  • Missing such as in Remotely Connecting section
• All relevant code examples written with backticks (```)
• All screenshots correspond to the described steps
• All titles of sections are formatted as headers or similar
• Lab report is on its own page, not the index page
• Last example counts keystrokes and shows how to run remotely saving time
  • Missing keystroke count
• Text is formatted in a way that was easy for grader to read

Additional comments from your grader:
Good job!

---

If you don't have all the checkmarks above, fix the issues described, and then submit a regrade request on Gradescope. Use this template for your regrade request:

• Link to this issue
• Link to your published lab report page

Lab Report 2 Feedback

Bug/Input 1

• Commit screenshot for bug/input 1
• Link to test file for bug/input 1
• Symptom shown as command + output for bug/input 1
• Description of relationship between bug, symptom, and input for bug/input 1

Bug/Input 2

• Commit screenshot for bug/input 2
• Link to test file for bug/input 2
• Symptom shown as command + output for bug/input 2
• Description of relationship between bug, symptom, and input for bug/input 2

Bug/Input 3

• Commit screenshot for bug/input 3
• Link to test file for bug/input 3
• Symptom shown as command + output for bug/input 3
• Description of relationship between bug, symptom, and input for bug/input 3

Additional comments from your grader:

• nicely done!

Feel free to comment below if you have any questions about the rubric/feedback.

---

If you don't have all the checkmarks above, fix the issues described, and then submit a regrade request on Gradescope. Use this template for your regrade request:

• Link to this issue
• Link to your published lab report page

Lab Report3 Feedback

Setup Github Access from ieng6

Here is your feedback for Lab Report 3 - Setup Github Access from ieng6:

• Show where the public key you made is stored on Github and in your user account (screenshot)
• Show where the private key you made is stored on your user account (but not its contents) as a screenshot
• Show running git commands to commit and push a change to Github while logged into your ieng6 account
• Show a link for the resulting commit

Additional comments from your grader:
Good job!

---

If you don't have all the checkmarks above, fix the issues described, and then submit a regrade request on Gradescope. Use this template for your regrade request:

• Link to this issue
• Link to your published lab report page

Lab Report 5 Feedback

Here is your feedback for Lab Report 5:

• Explains how tests with different results were found (diff, manual search, etc)

Test 1:

• Describes which, if any, implementation is correct by showing both actual outputs and indicating what the expected output is
• Describes bug in code for one of the incorrect implementation and shows the code that should be fixed.

Test 2:

• [] Describes which, if any, implementation is correct by showing both actual outputs and indicating what the expected output is
• [] Describes bug in code for one of the incorrect implementation and shows the code that should be fixed.

Additional comments from your grader:

Great job, but you forgot to do another test. Exact same thing as test 1 but a different test that had different outputs. Add that and resubmit and you should get a 100%!

Feel free to comment below any questions about the rubric/feedback

---

If you don't have all the checkmarks above, fix the issues described, and then submit a regrade request on Gradescope. Use this template for your regrade request:

• Link to this issue
• Link to your published lab report page