Skip to content

test(roster): pin the clock in the give-away test so it stops failing every run #3541

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.

Sign up for GitHub

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

Merged
BigSimmo merged 1 commit into from
Oct 14, 2026
Merged

test(roster): pin the clock in the give-away test so it stops failing every run #3541

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 6 additions & 0 deletions tests/roster-team-calendar-manager.dom.test.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -297,6 +297,12 @@ describe("Team calendar, manager layer", () => {
});

it("reads requests, manage and the roster again after a give-away is sent from the calendar", async () => {
// The give-away sheet reads the real clock (`useRosterNow()` is not handed the page's pinned
// `now`), and the shift (Thu 15 Oct, 09:00 Perth) counts as urgent inside 24 hours, which swaps
// "Offer to 1 person" for "I can't make it". This test only ever passed because the real date
// was more than a day before the fixture shift; from 09:00 Perth on 14 Oct 2026 it failed on
// every run. Pin Date to two days before the shift so the ordinary give-away path is the one tested.
vi.useFakeTimers({ toFake: ["Date"], now: new Date("2026-10-13T00:00:00Z") });
const { posts, reads } = mockFetch();
render(<RosterTeamPage now={NOW} />);
fireEvent.click(await screen.findByRole("button", { name: /You, Day 09:00–17:00/ }));
Expand Down
Loading