search

dhruvir29 / pe

0 stars 0 forks source link

Missing extension for use case view #8

Open dhruvir29 opened 10 months ago

dhruvir29 commented 10 months ago

Missing extension for when the user does not indicate any class index

nus-se-script commented 10 months ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Use case DG View

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

For Use case: View all the information about a class, there is a missing extension - The user not adding a valid index. Although step 1 says that "User chooses a class out of all the classes they are teaching", if they enter the name of the class instead of the index, there would be an error. Hence an extension should be added for invalid index.

[original: nus-cs2103-AY2324S1/pe-interim#5073] [original labels: severity.Low type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Issue accepted as there should be another extension.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: This bug report is talking about the missing extension for the use case for View for when the user does not specify anything for the class index (ie they simply type in "view /c"). This is a different extension from the one specified in the bug report "Use case DG View", which is talking about the use case missing an extension for when the user adds in an invalid class index (ie a class index that is out of bounds or that is non-numerical). Hence, these two bug reports are covering 2 separate extensions that should have both been added to the use case.

I believe that the two bug reports are separate and cover two separate extensions that should have been added, and thus should not be duplicates. I believe both should have been handled as separate extensions for the use case for view as can be seen by how this has been done for the use case for marking a student as seen below.

Screenshot 2023-11-21 233549.png

[Note that the image above is another use case in the DG (for mark), and not the use case that this bug report is talking about. It is simply used as an example to show that the extension in this bug report and the other bug report were written down as separate extensions for another feature, which proves that the bug reports are not duplicates.]

Hence I do not think they are duplicate bug reports.