charvishukla / cse15l-lab-reports

cse15l-lab-reports

Go to https://charvishukla.github.io/cse15l-lab-reports/

cse15l-lab-reports's Issues

Lab Report 4 Feedback

Here is your feedback for Lab Report 4:

• Provides a link to their markdown-parse repository
• Provides a 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:

---

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:

• Provides correct description of how mismatch in outputs was identified
• Correct markdown formatting.
• Lab report is on its own page, not the index page.

Test File 1

• Describes which implementation is correct
• Shows actual output and the expected output
• Provides correct description of the bug
• Provides code snippet that needs to be changed

Test File 2

• Describes which implementation is correct
• Shows actual output and the expected output
• Provides correct description of the bug
• Provides code snippet that needs to be changed

Additional comments from your grader:
Great work!

Feel free to comment below with 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 1 Report Feedback

Here is your feedback for Lab Report 1:

• All relevant URLs written as markdown links
• 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 shows how to run remotely saving time
• Text is formatted in a way that was easy for grader to read

Additional comments from your grader:
Great job on the report!

---

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

Here is your feedback for Lab Report 2:

• Correct screenshot of code diff page
• Correct failure inducing test file - 1
• [] Correct failure inducing test file - 2
• [] Correct failure inducing test file - 3
• Screenshot of symptom output that caused the failure for test file - 1
• [] Screenshot of symptom output that caused the failure for test file - 2
• [] Screenshot of symptom output that caused the failure for test file - 3
• Correct description for the relationship between the bug, the symptom, and the failure-inducing input for file - 1
• [] Correct description for the relationship between the bug, the symptom, and the failure-inducing input for file - 2
• [] Correct description for the relationship between the bug, the symptom, and the failure-inducing input for file - 3
• Correct markdown formatting
• Lab report is on its own page, not the index page
• [] Text is formatted in a way that was easy for grader to read

Additional comments from your grader:
There should be 3 cases of test files that failed (see the rubric above). Also, your 2nd link on gradescope should be to the repo that holds you lab reports.

---

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

Here is your feedback for Lab Report 3:

• Correct markdown formatting.
• Lab report is on its own page, not the index page.
• Correct screenshot of .ssh/config file
• Show the ssh command logging you into your account using just the alias you chose.
• Show an scp command copying a file to your account using just the alias you chose.
• Correct description of streamlining ssh configuration.
• Screenshot of where the public key you made is stored on Github and in your user account.
• Screenshot of where the private key you made is stored on your user account.
• Show git commands to commit/push a change while logged into your ieng6 account.
• Show a link for the resulting commit.
• Correct description of setting up Github access from ieng6.
• Show copying your whole markdown-parse directory to your ieng6 account.
• Show logging into your ieng6 account and compiling/running the tests for your repository.
• Show combining scp, semicolon, and ssh to copy the whole directory and run the tests in one line.
  The shown command doesn't run the java tests on the remote server but would rather try running them locally. Hint: Check Lab 1 last part, and piazza post @444 on how to run the command in one line.
• Correct description of copying whole directories.

Additional comments from your grader:
Show your ieng6 key in GitHub.com. Also include a screenshot of successfully pushing code changes from your ieng6 account. Include the link to the commit as well.

---

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