Repository navigation
Add price selection coverage to the car insurance quote wizard - #2
michaustriaqa wants to merge 3 commits into
Conversation
Extends the wizard flow past product data into price selection: waits for the asynchronously-loaded price plans (the step whose reliability was previously unconfirmed), selects a plan via the same styled-radio sibling-click pattern used for gender, and submits via the same JS-dispatched click pattern already used for the other "next" buttons. Verification of this specific step against the live app is pending - its price-plan load was the one thing observed to be unreliable during the original investigation, before the WebDriver click fix. This commit is unverified against CI until pushed.
Direct evidence from CI: after submitting product data and clicking next, the price-plan loading spinner appears but no price-fetching XHR/fetch request is ever made (Performance API captured zero requests after a 10s wait). This isn't a slow response or a timing issue that a longer wait could fix - the live application's price computation step simply never gets triggered under headless Chrome automation in CI. This confirms the concern already noted in the README's "Known limitations" section before this was attempted: the price-plan step's reliability under automation is a live-app issue, not something in this test suite's control. Reverting to the last known-good state (ending coverage at product data acceptance) rather than shipping a step that fails unpredictably.
Closing without mergingAttempted to extend coverage past product data into price selection, but it turned out to be genuinely unreliable against the live application, not a bug in this test suite. Evidence: after submitting valid product data and clicking "next," the price step's loading spinner ( This confirms the concern already flagged in the README's "Known limitations" section. Reverted the branch back to the last known-good state (ending coverage at product data acceptance); there's nothing left in this PR to merge. If this step's reliability under automation can be confirmed some other way in the future (e.g. it turns out to depend on a header, cookie, or interaction headless Chrome doesn't provide), extending coverage to price selection remains a reasonable follow-up. Generated by Claude Code Generated by Claude Code |
2 participants
Summary
Extends the car insurance quote wizard test coverage (from #1) past product data into price selection:
resources/pages/price_option_page.resource— price plan selection (silver/gold/platinum/ultimate), using the same styled-radio sibling-click pattern already established for gender selection, since these controls use the same idealforms styling.Wait Until Element Is Visible ... timeout=45s) before attempting selection — this asynchronous load was the one step whose reliability was left unconfirmed in Restructure into a full UI + API test portfolio with Page Object Model #1, before the WebDriver-click fix for the wizard's "next" buttons was found. This PR re-verifies it against the live app now that fix is in place.Price Option Should Be Acceptedverifies the wizard genuinely advanced to the send-quote contact form (a concrete next-step indicator), not just that no exception was thrown.Quote submission (the contact/registration form after price selection, with email/password/etc.) remains out of scope, per the same "Known limitations" reasoning as before.
Test plan
robot --dryrun tests— all test cases parse and resolve keywords correctlyrobocop check/robocop format --check— cleanGenerated by Claude Code