• Tests to confirm that the form is only valid if all required fields are completed
• Tests to confirm that only the necessary field are displayed on the form

• Tests are run to confirm that the form is only valid if all required fields are completed
• Tests to confirm that only the necessary field are displayed on the form
• Not tested: Confirm field is read-only/disabled.

• Create a booking
• Update/make changes to a booking
• Delete a booking
• Mark a booking as cancelled

• An email is sent to the restaurant admin advising of the new booking
• The booking is listed on the user's booking listing
• for each line item a 'Change' and 'Cancel' button is activated

• once a change is made to booking, if the booking had already been confirmed by restaurant admin, the status of the booking will be reset from confirm='Yes' to confirm='No'

• Delete option/button was replaced by the cancel button
• On deleting a booking an email is sent to the restaurant admin

• When a user cancels a booking confirm is set to 'Cancel'
• The option to cancel a booking is preferable, as the record will still be visible to the admin
• Once the user cancels the booking, the booking is no longer displayed to the user
• On cancelling a booking an email is sent to the restaurant admin
• Functionality can be added later to provide conditions permitting a user to delete a booking

• Only open tables are displayed

• An email is sent to the admin with the content of the content form
• The contact table is updated with the content of the content form

• New users will receive and email to validate their account

CSS

• No errors were returned by W3C validator on bus-casual-styles.css
• No errors were returned by W3C validator on styles.css

Lighthouse

• I ran the lighthouse report to rate my website's performance, accessibility, best practices and SEO.

• because some styles sheets and images definitions in the template were not in block tags
• Also added {% load static %} to all templates due to block end error

• installed whitenoise package

• After hours of figuring out how "it" works, then going through error after error, the brain swells and the simplest typo is blocked from your sight

• previously working (somehow) with two parameters, def confirm_booking(self, queryset):, when simply changing confirm from 0 to 1 and vice versa. 0 being No and 1 being Yes.
• after changing the field type from integer to char and adding an additional option of 'cancel' I received this error:
  • confirm_booking() takes 2 positional arguments but 3 were given
• After scouring the web for possible causes I came up empty handed. I decided to look deeper into the detail and found my solution from looking into:
  • File "/workspace/.pip-modules/lib/python3.8/site-packages/django/contrib/admin/options.py", line 1408, in response_action response = func(self, request, queryset)
• Adding 'request' as a second parameter solved the issue: def confirm_booking(self, request, queryset):

• after changing confirm field from integer to char in booking model I didn't remove the conditional statement from the booking template used to set confirm 0 to No and 1 to Yes. This displayed inconsistant values.

• Cause: the format on the booking_time field was: format=('%h:%m') instead of format=('%H:%M')

The link to the deployed app:

• https://herbsrestaurant.herokuapp.com/

• The app was deployed using the Heroku App