thekiddos / restaurant-sys Goto Github PK

Make sure there are no side effects

• Test adding entities with same id

• A transaction of transactions

• What happens to (Timecards, Classifications, ... etc) When deleting an an entity that relates to them

• Write tests for Relations (One-to-Many, ...)

Two types of Employees Salaried And Hourly Salaried

Save the invoice in the database
Instead of deleting stuff they should be moved to another databse/table or Marked as history

After a certain amount of time (eg: 15 minutes for most restaurants) of the specified reservation time
the user is promoted if the reservation should be canceled

For example if the customer moved from one table to another all his previous orders should also be altered to reference the new table.

Some tests are dates dependent meaning they will fail in the future
Tests causes minor issues because they run together interfering with the database for another test

When changing an employee classification what should happen to his current pay for example if he was hourly paid?

There should be 2 kinds of booking immediate and scheduled

With Multiple Ctrl+Z

for example don't give a salaried employee his salary if he didn't show up for a long time

for hourly employees only

A question or a game for the customers who ever wins gets a discount/free thing

When the PayDayTransaction is executed it should give a summary of the Paychecks and promots the user for several actions:

• cancel a certain paycheck
• cancel the whole transaction
• procced with the transaction