-
Notifications
You must be signed in to change notification settings - Fork 1
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
[CPDNPQ-2419] Fix some flakey tests #2095
base: main
Are you sure you want to change the base?
Conversation
Review app deployed to https://npq-registration-review-2095-web.test.teacherservices.cloud/ |
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - great work debugging these - flaky specs are always a pain to debug.
Only query is if reload
ing only on later usage leaves the earlier lines still being flaky?
@@ -20,7 +20,7 @@ | |||
expect(page).to have_css("td:nth-child(1)", text: voided_declaration.id) | |||
expect(page).to have_css("td:nth-child(2)", text: voided_declaration.user.id) | |||
expect(page).to have_css("td:nth-child(3)", text: voided_declaration.declaration_type) | |||
expect(page).to have_css("td:nth-child(4)", text: voided_declaration.course.name) | |||
expect(page).to have_css("td:nth-child(4)", text: voided_declaration.reload.course.name) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the declaration is needing to be reloaded, presumably because data may have changed, shouldn't the first usage of the declaration on line 20 be the one doing the reload?
Context
Ticket: https://dfedigital.atlassian.net/browse/CPDNPQ-2419
tl;dr: fix some flakey tests — think I got them all, but some of the failures are veeeery intermittent and can't be reliably reproduced even with the same seed! So we'll have to wait and see.