Open marcuschj opened 3 years ago
Entering payment
as a command does not show all the payment-related commands available as stated in the UG.
As shown in the result panel, all the payment-related commands are listed when you type in payment
. If you scroll down the result panel, you will see all the payment-related commands available.
An error message is returned instead.
Stating that Entering payment shows you all the payment-related commands available
, is because we want the user to have an easier way to obtain the overview of all payment commands so that there is a consolidated place to understand all the commands.
The error message is returned in order to maintain consistency with the other commands, since payment
is not executed, just like how delete
by itself is an error.
For example, typing delete
without the INDEX
will return an error message showing the correct syntax of the command. Similarly, we apply the same logic to the payment
command where we return an error message alongside how to use payment-related commands.
Team chose [response.Rejected
]
Reason for disagreement: There is no tester's response. I cannot accept the rejection if there is no evidence to back this rejection up
Team chose [type.DocumentationBug
]
Originally [type.FeatureFlaw
]
Reason for disagreement: I classified this as a Feature Flaw because the command payment
promises a certain behaviour, but this was not provided in the application.
Team chose [severity.VeryLow
]
Originally [severity.High
]
Reason for disagreement: There is no tester's response. I cannot accept the rejection if there is no evidence to back this rejection up
Entering
payment
as a command does not show all the payment-related commands available as stated in the UG.An error message is returned instead.