frederickemerson / pe

0 stars 0 forks source link

No check for same test name #2

Open frederickemerson opened 2 weeks ago

frederickemerson commented 2 weeks ago

no check for same test names i was able to create multiple programmes with the same name image.png

nus-se-script commented 1 week 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

Thank you for pointing out this behavior. After careful consideration, we would like to clarify that allowing duplicate programme names is intentional and aligns with the nature of our product design.

We do not enforce unique names for programmes, exercises, or days because our functionalities rely on the index of these items rather than their names. This design choice ensures flexibility for users, allowing them to manage their data in a way that suits their individual preferences. Additionally, this approach does not affect any other functionalities in our application.

This also matches the use case for the app as we do not expect users to want unique names for their programmes. For example, users could have 2 programmes named "PPL" with slightly different variations when they're experimenting with their routines.

We feel it does not make sense to restrict the user from doing this for these reasons and thus do not believe this to be a valid feature flaw.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your reason]


## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]