Description
automation/tests/organizationTransactionTests.test.ts has skipped scenarios covering the next-transaction button in Ready to sign and History flows. Review whether the current UX still supports these transitions and make the tests reliable around transaction ordering and navigation state.
The goal is to restore confidence that users can move through multiple transactions without returning to the list view each time.
In scope
organizationTransactionTests.test.ts:405 Verify next button is visible when user has multiple txs to sign
organizationTransactionTests.test.ts:416 Verify user is redirected to the next transaction after clicking the next button
organizationTransactionTests.test.ts:430 Verify next button is visible when user has multiple txs in history
Acceptance criteria
- The next-button scenarios are restored or replaced with equivalent passing coverage.
- The tests verify both button visibility and successful navigation to a different transaction.
- The scenarios are stable in repeated CI & local runs.
Description
automation/tests/organizationTransactionTests.test.tshas skipped scenarios covering the next-transaction button in Ready to sign and History flows. Review whether the current UX still supports these transitions and make the tests reliable around transaction ordering and navigation state.The goal is to restore confidence that users can move through multiple transactions without returning to the list view each time.
In scope
organizationTransactionTests.test.ts:405Verify next button is visible when user has multiple txs to signorganizationTransactionTests.test.ts:416Verify user is redirected to the next transaction after clicking the next buttonorganizationTransactionTests.test.ts:430Verify next button is visible when user has multiple txs in historyAcceptance criteria