search

vishnuvk47 / pe

0 stars 0 forks source link

Incorrect output when input is in wrong order happens with list command as well #15

Open vishnuvk47 opened 1 year ago

vishnuvk47 commented 1 year ago

Screenshot 2023-04-14 at 5.19.10 PM.png

Should be handled as an exception or input be read as appropriate using flags

soc-se-bot commented 1 year ago

Team's Response

Should be a featureflaw as it deals with the order of the flags.

Severity should be low as it only appears in rare situations when a user does not follow the intended formatting. It does not affect the normal operations according to the tester's bug report.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: In command-line interface (CLI) based applications, the order of flags is usually not important which includes most of the git commands that can be used via CLI and some users that want to use CLI based apps may be accustomed to this practice, and users expect to be able to specify parameters in any order they choose. Therefore, if there is no explicit specification regarding the order of parameters in the user guide or documentation, users may assume that they can use them in any order.

Nowhere in the UG is it stated that the commands must be executed in a specific order, which is a crucial point to consider when the program uses flags to track input. However, if the program does NOT use flags, it can be assumed intuitively that the commands need to be in a certain order. In light of this, it opens the question of why flags are used if the order cannot be changed. Additionally, if the order does matter, it may be better to eliminate the use of flags altogether, as this would remove the need for users to type the special character "/" and reduce the number of characters they need to input by six. This would optimize the program for its intended audience and facilitate faster typing.

Guidelines describe feature flaw as: Missing features and problems in how a feature is designed are considered feature flaws i.e., type.FeatureFlaw.

I did accidently identify this bug as a functionalityBug however as the team noted this is indeed a feature flaw and cannot be rejected.

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