search

HalphasX / pe

0 stars 0 forks source link

Issue : Testing out Add Schedule #4

Open HalphasX opened 2 years ago

HalphasX commented 2 years ago

The example shown in the add schedule for adding event is as shown below. Bug2.png

However, as I was testing to add the schedules with respect to the examples, it causes my laptop to stop responding for a while and the CPU started heating up. This might be due to a weaker hardware system, however, I don't think it's a good idea to put an example that can cause someone's laptop to crash into the UG. There is also no indication in the DG that there is a limitation to run this command. Suggestion: Either state it in the documentation or make the commands run faster.

nus-pe-bot commented 2 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]

Docs: Adding schedule issue

The UG indicated that the format of adding an event is as follows:

Bug Add Schedule command.png

However, when I tested out as the format above shown, it fails. Bug.png

I believe this is due to the documentation being written up wrongly, rather than it not working functionally. (Should be fr/ instead of from/

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

Their Response to the 'Original' Bug

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

No details provided by team.

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 is absolutely not the same issue with the duplicate ones. The duplicate issue indicates that there is a typo when testing out the add feature in the example, as the format indicates from instead of fr when using the command. The current issue indicates that when trying out the recurd inside the add feature, it causes my pc to stop responding for a while. This is not the same bug, and hence should not be a duplicate.

:question: Issue type

Team chose [type.DocumentationBug] Originally [type.FeatureFlaw]

Reason for disagreement: For the same reason I put in the duplicate issue, this is a feature flaw. The NFR did not indicate anything about the application lagging with lower hardware systems, and my pc just stopped responding when running the commands shown in the examples.

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Medium]

Reason for disagreement: This aims towards users who have hardware limitations. Imagine testing out an example in the product and suddenly having your pc stop responding for a while and heating up. Since this does not apply to many users and the application will run after some time, I think that this is a medium severity feature flaw. Again, I think that the developer team thought that this is a duplicate of what is stated above, but it is different. I suggested that the developer should change the example to avoid this from happening, as testers with hardware limitations might have difficulty running this command without having their pc slow down in the process.