Skip to content

Make the harness scenarios independent of their run order #448

Open

Description

@hpmaxi

Priority

Low

User story / Problem statement

The harness scenarios share one deployed network, and some depend on what an earlier scenario left there. CI runs them in a fixed order: deploy, test:happy-path, test:sep40, test:guards, test:wind-down. On a local network, deploy then test:sep40 then test:guards (skipping test:happy-path) failed one guards test, "two epochs pending at once > each keeps the price it was fulfilled at", with refused: DeviationExceeded. In CI order it passes. The order is not written down anywhere a person running a single scenario would see it.

Expected outcome

Either each scenario sets up the oracle price it needs, or the harness README states which scenarios must run first.

Acceptance criteria

  • The cause of the DeviationExceeded refusal out of CI order is identified
  • Each scenario passes after deploy alone, or the harness README lists the required order

Activity

  1. hpmaxi commented on Nov 16, 2026

    @hpmaxi
    ContributorAuthor

    Another order dependency, found while running the scenarios locally for #458-#461: test:queue fails after npm run seed. The seed's demo step leaves the open epoch with pending requests on purpose, and redemption-queue.test.ts assumes the open epoch is empty. It passes once that epoch is sealed and priced. Neither seed nor test:queue runs in CI today, so nothing is red, but a person running them in that order hits it.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestepic:infraCI, footprint, TTL keeper, reproducible deploypriority: lowtranche-3Grant Tranche 3 work

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions