Agentum07 / pe

0 stars 0 forks source link

Lack of screen shots for Manual Testing Add command #18

Open Agentum07 opened 3 years ago

Agentum07 commented 3 years ago

Unable to see what the app would look like when the given commands have been entered, given I don't have access to the app now.

Becomes too wordy.

Screenshot 2021-11-12 172951.png

nus-pe-bot commented 3 years ago

Team's Response

No details provided by team.

The 'Original' Bug

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

lack of screenshots for manual testing delete command

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.


Unable to see what the app would look like when the given commands have been entered, given I don't have access to the app now.

Becomes too wordy.

Screenshot 2021-11-12 173151.png


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

Their Response to the 'Original' Bug

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

Hi thanks for the input. The lack of access to the app is actually an artifiical constraint imposed due to the PE, so it should not be an issue for normal users. The expected response of the app is also written, and it isn't too long, so we do not think this is an issue. In fact, actually the GUI outcome of deleting an entry is probably exactly what one would expect, and we feel that adding more screenshots provides little value, so we did not want to clog up the UG unncessarily.

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: The way the add command works is the complete opposite of the delete command. Given that I don't have screenshots for either of the commands, I cannot figure out how the app looks after execution of either command.


:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: > so we did not want to clog up the UG unnecessarily.

Manual testing is written in the DG and not the UG.

The lack of access to the app is actually an artificial constraint imposed due to the PE, so it should not be an issue for normal users.

I have to disagree with this. If I am a prospective developer reading the DG on my phone/tablet/iPad, I cannot execute the product. Real life example: As a student on the lookout for apps to make my life easier, I do read documentation on my phone on my way to class.

The screenshots ensure that the DG is self contained and users don't need to keep juggling between the app and the DG to see how different commands affect the app.