Test Scenario: Verify default-party quick-login end to end
Table of Contents
- Scenario Info
- Steps
- Barclays provisioning sets tenant_admin's default party
- Account info confirms the default party is set
- Login with quick-login ticked and a single default party skips the picker
- Multi-party account: quick-login ticked bypasses the picker
- Multi-party account: quick-login unticked shows the picker
- Multi-party account with no default set falls back to the picker
- Quick-login failure falls back to the picker, not an error
- Results
- Notes
This page documents a test scenario verifying all three tasks of Add a default party per account with a quick-login checkbox end to end: the default_party_id field (task 1), the login dialog checkbox (task 2), and provisioning setting the default (task 3). It is filled in with the target dialog and checklist of steps before testing starts; the QA Validation Runner panel rewrites * Results in place on save.
Scenario Info
| Field | Value |
|---|---|
| Verifies task | Add default_party_id field, Add quick-login checkbox, Update provisioning scripts |
| Parent story | Add a default party per account with a quick-login checkbox |
| Target dialog | LoginDialog |
| Clients | |
| State | PENDING |
Steps
Each step is its own heading — the title should be short (it's shown
as a single list entry in the QA Validation Runner); put any longer
instructions in the body below the title. The panel writes each
step's PASS/FAIL/PENDING outcome and notes back as a *** Result
child heading directly under it.
Barclays provisioning sets tenant_admin's default party
Run compass shell -f barclays_system_provision.ores (or the
equivalent Qt script library entry) against a freshly recreated
database. Confirm the script completes with no errors, including the
new "✓ Default party set to 'BARCLAYS PLC'." line after the
provision party step.
Result
| Field | Value |
|---|---|
| Status | PASS |
Account info confirms the default party is set
From the shell (or accounts info tenant_admin@barclays_plc),
confirm the account's default_party_id is populated and matches the
BARCLAYS PLC party's UUID (cross-check against parties list).
Result
| Field | Value |
|---|---|
| Status | PASS |
| Notes | Initially FAILED: an admin-scoped "Set as Default" right-click action wrote directly via NATS, bypassing Save/change-reason/version history. Reworked into a regular "Default Party" combo (Parties tab, sorted alphabetically, below the assignment list) that goes through the normal Save flow like every other account field. Re-tested PASS. |
Login with quick-login ticked and a single default party skips the picker
Log in to the Qt app as tenant_admin@barclays_plc with the "Log in
to default party" checkbox ticked (default state). Since this account
has exactly one party, the server auto-selects it — confirm login
completes straight to the main window with no picker dialog (this
path is unaffected by the checkbox; included as a baseline).
Result
| Field | Value |
|---|---|
| Status | PASS |
Multi-party account: quick-login ticked bypasses the picker
Using an account associated with two or more parties where one is set
as the default (e.g. via accounts set-default-party from the
shell), log in with the checkbox ticked. Confirm the login goes
straight to the main window logged into the default party — no
PartyPickerDialog appears — and the party shown in the app matches
the configured default.
Result
| Field | Value |
|---|---|
| Status | PASS |
Multi-party account: quick-login unticked shows the picker
With the same multi-party account, untick "Log in to default party"
before logging in. Confirm PartyPickerDialog appears as before, and
selecting a party (including a non-default one) completes login
normally.
Result
| Field | Value |
|---|---|
| Status | PASS |
Multi-party account with no default set falls back to the picker
Using a multi-party account with no default_party_id set, log in
with the checkbox ticked. Confirm PartyPickerDialog appears (no
default to quick-login to), and selection completes login normally.
Result
| Field | Value |
|---|---|
| Status | PASS |
Quick-login failure falls back to the picker, not an error
(If feasible to simulate — e.g. temporarily revoke the account's
membership of its stored default party server-side.) Log in with the
checkbox ticked. Confirm the app falls back to showing
PartyPickerDialog rather than failing the login outright.
Result
| Field | Value |
|---|---|
| Status | PASS |
Results
| Field | Value |
|---|---|
| Status | PASSED |
| Completed at | 2026-07-12T09:56:00Z |
| Branch | feature/add-default-party-id-field |
| Commit | 401b2e30c |
| Worktree | prime_origin |