kageyamajie / pfizer-pharmacy Goto Github PK

The problem i have faced in the Sales Module, the sales module, is the user can select member as customer type to get a 10% discount rate without checking the membership ID, second problem is the user can enter any random number act as credit card number, after that the customer still can purchase using credit card even though the credit card is invalid.

Bugs 1:
The system able to return the stock quantity that are more than the quantity on hand. The current quantity of the stock in the database is lower than the required quantity that user want to be return, logically this should not be able to run. For example, current stock quantity for Product A is 10, user want to return 12, logically it should fail due to not enough stock to be return.

Bugs 2:
User able to enter alphabet in the quantity field and it will force the system to be freeze due to wrong input entered and the system are not able to perform anything since there are an error occurred.

Now i have faced 2major problems on Employee Module which are in edit employee module, where the user entering the ID of the employee into the system to retrieve the detail of that particular employee. If the user entering the ID where it is not existed in the database, therefore it will cause the null error back to user and another problem is that most user will make is during the entering integer formatting data to the field such as Employee bank account number, salary, and contact number. The user might enter incorrect data into the da2tabase and caused data type compromised, for instance, when the user entering the employee contact number “016 1111 1110” but the user entered “016 1111 111o” which there is a character ‘o’ appear in the contact number.

First problem:
The membership ID is manually entered by the user. If the user entering the ID where existing the database long time ago, it will cause data redundancy in the Membership data file.

Second problem:
There is unidentified problem that most of the user do not meet or without intend to trigger it. The problem only occurs when the user retrieve and prepare to update the particular detail at the same time, the user want to delete that particular record same as retrieved for update. If the user delete the record first, so that the user back to update membership there, the data will still leave on the text field and the user still able to press on the update button and prompt a successful update message.

I found that there are two problem in the login module, the first problem is whenever user enter a correct password with a wrong user name the user still able to login to the system.
Second problem is when user enter wrong user name and wrong password the system do not give any message. So the user does not know whether the system is hanging or the user have entered wrong user name or password.

Bug 1: Product Price format

One of the constant problem that user will make is the numbering formatting, price is a numeric format with any character in between price format. Sometimes the user will key in character in accidentally. If the character being key into price field, it will resulting in the database side that there is a data type being compromised as character or string cannot compact with double data type.

Bug 2: Missed out essential data

In the product module’s create module, all the data are require to enter in the field in order the control tier can get the data from the interface pass into domain part. Sometime, the user will missed out one essential detail need to key in. For example, the user want to register a product, after fill in the detail, the user forget to enter the product’s name after click on the “registration”, so in the database side, there is a product record that leave the product’s name blank or null.

I found that are some minor mistake on constructing the user stories, such as, declare admin as a manager.