Description
automation/tests/organizationTransactionTests.test.ts has skipped observer-related scenarios covering transaction details, Ready for execution visibility, and DB linkage for observer assignments. Review whether the underlying observer feature changed or whether the tests are failing because of synchronization and environment issues.
The goal is to restore coverage for both user-facing observer behavior and the persisted transaction-observer relationship.
In scope
organizationTransactionTests.test.ts:339 Verify observer is listed in the transaction details
organizationTransactionTests.test.ts:366 Verify transaction is visible for an observer while transaction is "Ready for execution"
organizationTransactionTests.test.ts:386 Verify observer is saved in the db for the correct transaction id
Acceptance criteria
- Observer-related scenarios are no longer skipped.
- Coverage verifies UI visibility and DB linkage where applicable.
- The restored tests are stable in repeated CI & local runs.
Description
automation/tests/organizationTransactionTests.test.tshas skipped observer-related scenarios covering transaction details, Ready for execution visibility, and DB linkage for observer assignments. Review whether the underlying observer feature changed or whether the tests are failing because of synchronization and environment issues.The goal is to restore coverage for both user-facing observer behavior and the persisted transaction-observer relationship.
In scope
organizationTransactionTests.test.ts:339Verify observer is listed in the transaction detailsorganizationTransactionTests.test.ts:366Verify transaction is visible for an observer while transaction is "Ready for execution"organizationTransactionTests.test.ts:386Verify observer is saved in the db for the correct transaction idAcceptance criteria