search

eunrcn / pe

0 stars 0 forks source link

Before Delete is not followed by after delete #7

Open eunrcn opened 3 months ago

eunrcn commented 3 months ago

Screenshot 2024-04-19 at 4.25.08 PM.png

soc-pe-bot commented 3 months ago

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

No details provided by team.

The 'Original' Bug

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

Missing label for diagram in UG

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.

There should be a label in the last diagram for example "After delete:" similar to the first 2 diagrams to complete the flow of the story it is trying to tell image.png

[original: nus-cs2103-AY2324S2/pe-interim#4803] [original labels: type.DocumentationBug severity.VeryLow]

Their Response to the 'Original' Bug

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

Thanks for pointing this out.

After discussions within the team, we have decided to label this bug as response.NotInScope.

Reason:

The use of Delete instead of the use of both Delete and After Delete as labels is intentional as the use of both images is required to show the deletion process as a whole. The first image is technically a combination of both "during" and "after", the command being typed in the top box depicts the "during" and the result given by the application in the bottom box serves as the "after", thus it would not make sense to label the first image as simply During Delete and therefore splitting the two images into two separate labels would not be correct.

We thus opted for the simpler option of combining both images and labelling it as the Delete process.

Note: While response.NotInScope are not counted against the dev team, they can earn a small amount of consolation marks for the tester. The other three do not affect marks of either the dev team or the tester.

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: [replace this with your reason]

## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]