tnsyn / pe Goto Github PK

update-order command allows client ID to be an invalid client ID (i.e. client does not exist).

Steps to recreate:

1. Run the update-order command and change the --client field to any client ID that does not exist on the list.

Missing information on what the valid parameters are for fields like phone, name or email. This information is later mentioned under the Commands section, but the format of the UG is such that users will read the GUI section first, information should be given here as well.

When an update-client command is run with invalid format, error is not handled properly and app does not respond.

Steps to recreate:

1. Type in the command 'update-client --name Alex'.

The example command that the users run should be stated before the screenshots, as the screenshots do not reflect what the command is.

After editing a client in the sidebar and saving the edits, or after deleting a client, an empty sidebar persists on the right and does not automatically close.

Steps to recreate:

1. Double click on a client.
2. Edit the client and press save.

UG states that upon opening the application, a list of sample clients will be displayed in the application. However, my app shows an empty list.

Steps to recreate:

1. Place JAR file inside empty folder.
2. Run the JAR file with java -jar command.

Editing an order allows an invalid client index to be inputted under the 'Client ID' field.

Steps to recreate:

1. Edit an order.
2. Change Client ID to any 5-digit client ID between 1 and 99999 inclusive.

Adding/editing an order allows an address that does not match the address of the client. Might be counter-productive from the POV of the user.

Steps to recreate:

1. Add/edit an order.
2. Input any address.

After shrinking the screen upwards, the command box cannot be clicked on.

Steps to recreate:

1. Click anywhere (except for command box).
2. Shrink the screen upwards.
3. Click on the command box.

Glossary does not include a definition for the term "client".

Missing instructions for how to produce a filtered client list (if this is a feature the team intended).

When an update-order command is run with an invalid format, error is not handled and the app does not respond.

Steps to recreate:

1. Type in the command 'update-order --description lip-tint'.

Missing instructions for how to produce a filtered order list (if this is a feature the team intended).

Features are listed as a separate category from what looks like the features of the product. Upon clicking on the features section, the only information given is regarding the notation used throughout the UG, and not the features of the product.

Clicking on various links throughout the DG redirect to addressbook code base, instead of LogOnce's code base.

User stories are not formatted in a neat table (or other equivalents) for better readability.

Error message for invalid date when adding new order is "Text '___' could not be parsed at index 0'.

Steps to recreate:

1. Create an order.
2. Type any text under the date field.

Unnecessary UI details (e.g. LogOnce shows an error message/LogOnce shows a success message) are mentioned in the use cases.