Skip to content

fix(e2e): derive burndown current-month assertion from the clock #88

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
san360 merged 1 commit into from
Jun 3, 2026
Merged

fix(e2e): derive burndown current-month assertion from the clock #88

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: 5 additions & 1 deletion tests/e2e/burndown.spec.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,10 @@ test.describe('Burndown', () => {

test('shows current month', async ({ page }) => {
const content = await page.textContent('#content');
expect(content).toContain('May 2026');
// The burndown page defaults to the live current month (page-burndown.ts uses new Date()
// and formatMonthLabel's toLocaleString), so derive the expected label the same way
// instead of hard-coding it — otherwise the assertion goes stale every month rollover.
const expectedMonth = new Date().toLocaleString('default', { month: 'long', year: 'numeric' });
expect(content).toContain(expectedMonth);
});
});
Loading