bug: scope e2e homepage error selector to main's direct child #61

Merged

Gilles merged 1 commit from fix/e2e-accueil-selector-ambiguity into master

2026-11-02 07:55:56 +00:00

Gilles commented

2026-11-02 07:07:59 +00:00

Owner

Summary

e2e/accueil.spec.ts's $("main p") matched both ProjectListView's own error paragraph and BigbDashboard's independent loading/error <p> (nested one level deeper, inside section.overview), so the assertion flaked depending on which of the two independent fetches had settled by sample time.
Scoped the selector to main > p (direct child), which is exactly ProjectListView's own paragraph — no timing dependency, no frontend change needed.

Closes #60

Test plan

CI e2e job green
Re-run e2e a few times (or check history) to confirm the flake is gone, not just hidden

🤖 Generated with Claude Code

https://claude.ai/code/session_014HiJrn6J6vhyFfC2qyY4uh

## Summary - `e2e/accueil.spec.ts`'s `$("main p")` matched both `ProjectListView`'s own error paragraph and `BigbDashboard`'s independent loading/error `<p>` (nested one level deeper, inside `section.overview`), so the assertion flaked depending on which of the two independent fetches had settled by sample time. - Scoped the selector to `main > p` (direct child), which is exactly `ProjectListView`'s own paragraph — no timing dependency, no frontend change needed. Closes #60 ## Test plan - [ ] CI e2e job green - [ ] Re-run e2e a few times (or check history) to confirm the flake is gone, not just hidden 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_014HiJrn6J6vhyFfC2qyY4uh

Gilles added 1 commit

2026-11-02 07:07:59 +00:00

bug: scope e2e homepage error selector to main's direct child

ci / test (pull_request) Successful in 3m30s

Details

ci / e2e (pull_request) Has been skipped

Details

ci / docker (pull_request) Has been skipped

Details

ci / deploy (pull_request) Has been skipped

Details

a9d28ef8a7

$("main p") matched both ProjectListView's own error paragraph and
BigbDashboard's independent loading/error <p> (nested one level
deeper), so the assertion flaked depending on which of the two
fetches had settled by sample time. Scoping to the direct child
removes the ambiguity without any timing dependency.

Closes #60

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014HiJrn6J6vhyFfC2qyY4uh

Gilles added the

bug

labels

2026-11-02 07:08:07 +00:00

Gilles commented

2026-11-02 07:31:53 +00:00

Author

Owner