Skip to content

Test: stabilize proposal confirmation feature spec - #3808

Open
RedZapdos123 wants to merge 3 commits into
openSUSE:masterfrom
RedZapdos123:fix-proposal-confirmation-spec
Open

Test: stabilize proposal confirmation feature spec#3808
RedZapdos123 wants to merge 3 commits into
openSUSE:masterfrom
RedZapdos123:fix-proposal-confirmation-spec

Conversation

@RedZapdos123

@RedZapdos123 RedZapdos123 commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Description:

Issue #3807 reported that spec/features/proposals_spec.rb could fail intermittently when a participant confirms a proposal.

This PR updates the proposal confirmation feature spec to avoid a stale Selenium node when the rails-ujs confirmation link redirects to the registration page.

It waits for the confirmation link to be present, triggers the click in the page context, and asserts the redirect with have_current_path.

Closes #3807.

Checklist:

  • I have verified the failing example from GitHub Actions run.
  • I have run ruby -c spec/features/proposals_spec.rb.
  • I have run git diff --check upstream/master...HEAD locally.

Additional validation:

  • Verified the real failure from GitHub Actions: rspec ./spec/features/proposals_spec.rb:162 # Event as a participant confirms a proposal failed with Node with given id does not belong to the document.

Signed-off-by: Mridankan Mandal <xerontitan90@gmail.com>
@RedZapdos123 RedZapdos123 changed the title test: stabilize proposal confirmation feature spec Test: stabilize proposal confirmation feature spec Jun 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Intermittent stale-node failure in proposal confirmation feature spec

1 participant