You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have just reseeded the database to include a gig with a date in the future - in order to test whether "gigs in the past are displayed differently" (as per the spec) and whether gigs in the past are "clearly labelled" (as per the user stories).
In the current state of the application, past and future gigs are not displayed differently (see screenshot below).
This is a significant problem because we simply cannot ship while the application doesn't meet the specified requirements.
Expected Behaviour
Gigs with dates in the past should be displayed differently, perhaps using grey and red instead of white and blue, as this would be intuitive for users.
Reproduction Steps
Clone repo and setup dependencies (see README.md)
Edit the date of one of the gigs in seeds/'test_gigs.sql' to be a date in the future, e.g. on line 15 change "2024-06-04" to "2024-12-04"
Seed the database with psql -h 127.0.0.1 giga -f seeds/test_gigs.sql -f seeds/test_users.sql -f seeds/test_bookings.sql
Run the application with python3 app.py
Navigate to localhost:5001/gigs
The text was updated successfully, but these errors were encountered:
Version
v4
Severity
High
Suggested Priority
High
Observed Behaviour
I have just reseeded the database to include a gig with a date in the future - in order to test whether "gigs in the past are displayed differently" (as per the spec) and whether gigs in the past are "clearly labelled" (as per the user stories).
In the current state of the application, past and future gigs are not displayed differently (see screenshot below).
This is a significant problem because we simply cannot ship while the application doesn't meet the specified requirements.
Expected Behaviour
Gigs with dates in the past should be displayed differently, perhaps using grey and red instead of white and blue, as this would be intuitive for users.
Reproduction Steps
-h 127.0.0.1 giga -f seeds/test_gigs.sql -f seeds/test_users.sql -f seeds/test_bookings.sql
python3 app.py
The text was updated successfully, but these errors were encountered: