nus-se-script
commented
6 days ago Team's Response
Thank you for pointing this out. The current implementation is the intended behavior, but the UG documentation was unclear in explaining the difference between the "forced setup" and "reset details" scenarios, resulting in confusion. I apologize for this inconvenience.
However, I believe that the CLI instructions provide sufficiently accurate guidance during the forced setup scenario. Users who follow the prompt on the CLI are asked to input only their gender and age, which is the intended behavior.
Thus, this bug is a documentation bug rather than a feature flaw. The documentation should be updated to accurately reflect the intended behavior of the application. Once again, thank you for pointing out this inconsistency between the documentation and implementation.
Items for the Tester to Verify
:question: Issue type
Team chose [type.DocumentationBug]
Originally [type.FeatureFlaw]
- [x] I disagree
Reason for disagreement: [replace this with your reason]
I believe that the bug FeatureFlaw still stands as this bug is both a FeatureFlaw and a DocumentationBug. Indeed, it is a DocumentationBug as the user guide did not have any mention on forced setup scenario. I also disagree that there in sufficient accurate guidance by the CLI instructions during the forced setup scenario as it only states please input your gender and add, with no example as well as how the input should be structured.
type.FeatureFlaw: Some functionality missing from a feature delivered in v2.1 in a way that the feature becomes less useful to the intended target user for normal usage. i.e., the feature is not 'complete'. In other words, an acceptance-testing bug that falls within the scope of v2.1 features. These issues are counted against the product design aspect of the project. Therefore, other design problems (e.g., low testability, mismatches to the target user/problem, project constraint violations etc.) can be put in this category as well.
As mentioned by the course website, this feature to set the age and gender of the user should allow the user to set his/her age and gender. Thus it should also work during the forced setup scenario by disallowing it to work during the forced setup scenario. This feature is less useful to the user for normal usage.
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** [replace this with your reason] severity.VeryLow : A flaw that is purely cosmetic and does not affect usage e.g., a typo/spacing/layout/color/font issues in the docs or the UI that doesn't affect usage. Only cosmetic problems should have this label. As mentioned in the course website, the label severite.VeryLow should only be used for cosmetic problems. In the dev team stand that this is a DocumentionBug, this is not just a simple typo/spacing/layout/colour/font issues in the docs or the UI that doesn't affect usage. If this forced setup scenario is essential to allow the app to start, this part should be in the user guide together with a quick start guide so that the user can understand and start the program. This surely affected usage even in the form of DocumentationBug. In my opinion that this is also a FeatureFlaw, this is definitely at least a severity.Low bug as it affects my usage of the product and caused my frustation that I was unable to start using the program despite multiple tries and I had to figure out the correct way to start using the app.
Initially, I kept following the format on the UG, set [gender] [age] but the it couldn't work, which made me wonder if there was something wrong with my input. I realised on the initial start of the app, it will just be inputting [gender] [age] which was not stated in the UG other than in the example for set. So the example for set is incorrect too.