Skip to content

Restore automation coverage for transaction observers in organization flows #2567

Description

@yasenltd

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Feature EnhancementEnhancing an existing feature driven by business requirements. Typically backwards compatible.Tests

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions