This suite follows work through the main menu, settings navigation and customer-defined record placements. Direct entry, menu selection and breadcrumbs are checked together so an administrator can identify the same destination whichever entry path is used. The suite also retains the planned ordering change as an explicit regression obligation.
The five scenario kinds are cumulative. Proposed cases remain executable work to assign; bound cases name the exact assertions reviewed and record no passing product run.
Custom placements can make an otherwise unfinished section useful. Settings replace daily navigation and need a return destination, while area offers depend on readable destinations. The recorded Accounting position remains a proposed assertion at these pins; the suite does not present its contrary baseline as passing evidence.
The proposed registry change is compared with the pinned baseline, with custom placements present.
Steps
Compare full and eligible application sequences with CRM and Accounting visible, hidden separately and without custom placements.
Expected
The proposed Accounting adjacency holds whenever both sections survive; other built-in order and placement behavior remain intact. The pinned baseline’s different order remains an implementation finding.
Data
An isolated browser context and run-owned association fixtures; deterministic authority, response and clock variants where specified.