test(wallets): assert address-generation status, not just dialog-open state

[Claudius-Maginificent]

TL;DR: Strengthen the "Add Receiving Address" regression test so it actually proves a new address was requested, not just that the dialog opened.

Detailed discussion

This is a test-only hardening change with no user-observable effect, so User story/Scenario are omitted per convention.

What was done

• Follow-up to fix(wallets): wire "Add Receiving Address" to the same flow as "Receive" #914 ("wire 'Add Receiving Address' to the same flow as 'Receive'"), which fixed the button but got squash-merged before this test-hardening commit could be pushed to the same branch — reapplied here as a standalone PR.
• The original kittest regression only asserted the Receive dialog's static "Core Address" label, which renders whenever the Core address type is selected — regardless of whether a new address was actually requested. A regression that reopens the dialog but silently drops the queue_core_address_request call would still have passed.
• Added an assertion on the "Generating a new address…" status label, which is only set when queue_core_address_request actually fires — so the test now proves the fix's actual behavior, not just a side effect of it.

Testing

• add_receiving_address_button_opens_receive_dialog kittest — PASS (cargo test --test kittest --all-features, narrowest relevant scope).
• cargo fmt --all -- --check clean.

Breaking changes

None.

Checklist

• Tests added
• No secrets in diff

Prior work

• Follow-up to fix(wallets): wire "Add Receiving Address" to the same flow as "Receive" #914 (merged) — the fix this test hardens.

Attribution

_{🤖 Co-authored by Claudius the Magnificent AI Agent}

[coderabbitai]

Warning

Review limit reached

@lklimek, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9953bc51-573a-4dbb-b623-92d864a1450b

📥 Commits

Reviewing files that changed from the base of the PR and between 5d225f2 and 453beb0.

📒 Files selected for processing (1)

• tests/kittest/wallets_screen.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test/add-receiving-address-status-assertion

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[thepastaclaw]

🕓 Ready for review — 47 ahead in queue (commit 453beb0)
Queue position: 48/49