Add information about writing tests

[ruishanteo]

Fixes #79

[mfjkri]

Hi Rui Shan! I believe this will be a great addition, as it allows students to follow along and learn about the various aspects of the code they need to write tests for as they go. I just have a few more additions for the tests based on the Git diffs in the tutorial.

[mfjkri]

Should we include the full test instead? For clarity and consistency

@Test
 public void execute() {
     assertCommandFailure(new RemarkCommand(), model, MESSAGE_NOT_IMPLEMENTED_YET);
 }

[ruishanteo]

Okay, done!

[mfjkri]

Since both the constructor and execute method of RemarkCommand was updated, how about phrasing this like this instead?

Since RemarkCommand now requires both an index and a remark for instantiation, the tests should be updated accordingly. Additionally, the execution of the command has been updated, so the tests should be adjusted to reflect these changes.

@Test
public void execute() {
   final String remark = "Some remark";

   assertCommandFailure(new RemarkCommand(INDEX_FIRST_PERSON, remark), model,
           String.format(MESSAGE_ARGUMENTS, INDEX_FIRST_PERSON.getOneBased(), remark));
}

[ruishanteo]

Amended it according to this too!

[Carlintyj]

Hello Rui Shan,

Great job on the proposed changes! I’ve reviewed your work, and I have a few additional suggestions that might help enhance the clarity and usefulness of the tutorial for the readers:

1. Explanation of @test Annotation: Perhaps you could consider including a brief explanation of what the @Test annotation does when you first mention it. This will help readers who may not be as familiar with JUnit understand its purpose and how it fits into the testing process.

2. Context for Test-Writing: At the beginning of each test-writing section, it might be helpful to add a sentence or two explaining why the tests are being written at that point in the tutorial. This provides context and highlights the importance of testing in the development workflow.

3. Link to JUnit Resources: Including a link to the official JUnit documentation or a relevant tutorial could be beneficial for readers who want to explore unit testing in more depth.

Thank you for your hard work and besides these, LGTM!

[damithc]

1. Explanation of @test Annotation: Perhaps you could consider including a brief explanation of what the @Test annotation does when you first mention it. This will help readers who may not be as familiar with JUnit understand its purpose and how it fits into the testing process.

@Carlintyj I'm not sure if we need this one. At this point students should have used JUnit in the iP already. We can point to the JUnit guide but we can't keep repeating all the basics in every tutorial :-)

[Carlintyj]

Okay, sounds good to me to just point to the JUnit guide. 😃 Thanks prof @damithc

[ruishanteo]

@Carlintyj

2. Context for Test-Writing: At the beginning of each test-writing section, it might be helpful to add a sentence or two explaining why the tests are being written at that point in the tutorial. This provides context and highlights the importance of testing in the development workflow.

Not sure what this refers to exactly. I have included short sentences/ clauses to explain why the tests are being written. For example: Since RemarkCommand now requires both an index and a remark for instantiation, the tests should be updated accordingly. Additionally, the execution of the command has been updated, so the tests should be adjusted to reflect these changes. Could you explain further/ give some examples on what this point refers to? Thanks!

3. Link to JUnit Resources: Including a link to the official JUnit documentation or a relevant tutorial could be beneficial for readers who want to explore unit testing in more depth.

Done! Added a link in the first panel.

[Carlintyj]

Since we created a new file RemarkCommand, we should also create a RemarkCommandTest file. JUnit tests are annotated with @test. For now, we expect execute in RemarkCommand to fail. Thus, the test will reflect this expectation.

I was thinking instead of saying we should also create RemarkCommandTest file as such, we could perhaps just drop a sentence or two to give further clarification. For example: "it’s crucial to ensure that our code behaves as expected. This is why we write tests at each step of the process. These tests not only verify that the new functionality works correctly but also help prevent future changes from inadvertently breaking the code."

Hope this clarifies my intentions.

[ruishanteo]

@Carlintyj
I see! I added that explanation to the main panel explaining that tests are written. I think that the line given was general so I added it to the introductory panel instead of the individual panels where tests are explained.

[jyue487]

Overall, LGTM! But are some of the contents overlapping with the Test section in IP?

[jyue487]

I am not too sure but should this be indented?

[ruishanteo]

Thanks! Added the indentation.

[damithc]

@ruishanteo Thanks for this PR.
I incorporated your changes in a4cf2b5