Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DS-3293 Updated opening times in integration test case to a future date #1038

Merged
merged 6 commits into from
Jan 6, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions test/integration/features/F006_Opening_Times.feature
Original file line number Diff line number Diff line change
Expand Up @@ -33,12 +33,12 @@ Feature: F006. Opening times
@complete @opening_times
Scenario: F006SXX6. Confirm recently added specified opening date can be removed from Dos
Given a basic service is created
And the change event is "open" on date "Jan 01 2025"
And the change event is "open" on date "Jan 01 2026"
When the Changed Event is sent for processing with "valid" api key
Then DoS is open on "Jan 01 2025"
Then DoS is open on "Jan 01 2026"
Given the change event has no specified opening dates
When the Changed Event is sent for processing with "valid" api key
Then there is no longer a specified opening on "Jan 01 2025"
Then there is no longer a specified opening on "Jan 01 2026"
And the service history is updated with the "removed" specified opening times

@complete @opening_times
Expand All @@ -55,29 +55,29 @@ Feature: F006. Opening times
@complete @opening_times
Scenario: F006SX8. Additional date changes open to closed
Given an entry is created in the services table
And the service is "open" on date "Jan 01 2025"
And the service is "open" on date "Jan 01 2026"
And the entry is committed to the services table
And the change event is "closed" on date "Jan 01 2025"
And the change event is "closed" on date "Jan 01 2026"
When the Changed Event is sent for processing with "valid" api key
Then DoS is closed on "Jan 01 2025"
Then DoS is closed on "Jan 01 2026"

@complete @opening_times
Scenario: F006SX9. Additional date changes closed to open
Given an entry is created in the services table
And the service is "closed" on date "Jan 01 2025"
And the service is "closed" on date "Jan 01 2026"
And the entry is committed to the services table
And the change event is "open" on date "Jan 01 2025"
And the change event is "open" on date "Jan 01 2026"
When the Changed Event is sent for processing with "valid" api key
Then DoS is open on "Jan 01 2025"
Then DoS is open on "Jan 01 2026"

@complete @opening_times
Scenario: F006SX10. Additional date changes times changed
Given an entry is created in the services table
And the service is "open" on date "Jan 01 2025"
And the service is "open" on date "Jan 01 2026"
And the entry is committed to the services table
And the change event specified opening is "open" from "10:00" to "16:00" on date "Jan 01 2025"
And the change event specified opening is "open" from "10:00" to "16:00" on date "Jan 01 2026"
When the Changed Event is sent for processing with "valid" api key
Then DoS is open from "10:00" until "16:00" on "Jan 01 2025"
Then DoS is open from "10:00" until "16:00" on "Jan 01 2026"
And the "service-sync" lambda does not show "report_key" with value "BLANK_STANDARD_OPENINGS"

@complete @opening_times
Expand Down
Loading