Skip to content
This repository was archived by the owner on May 17, 2026. It is now read-only.
This repository was archived by the owner on May 17, 2026. It is now read-only.

Document antipattern: Running features/scenarios in a specific order #696

Description

@aslakhellesoy

See https://cucumberbdd.slack.com/archives/C60TKS3SL/p1636399065115000

I strongly recommend you avoid relying on a specific order. When a scenario fails, you should be able to run just that scenario to reproduce the same result so you can fix it. If you choose not to follow that advice, you can specify the order by listing the feature files in your runner, or as command-line arguments, depending on what Cucumber implementation you are using.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions