Skip to content

/ config

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Specs rely on test order #198

Open
malakai97 opened this issue Feb 4, 2018 · 2 comments · May be fixed by #231
Open

Specs rely on test order #198

malakai97 opened this issue Feb 4, 2018 · 2 comments · May be fixed by #231
Assignees
@cjlarose
Labels
needs help
Milestone
3.0.0

Comments

@malakai97
Copy link

@malakai97 malakai97 commented Feb 4, 2018 •
edited

Description

Running the specs in a random order results in multiple failed specs, depending on the order's seed.

Rubies

  • 2.3.4
  • 2.4.2 - appraisal will not run the entire suite regardless of errors encountered

Steps to Reproduce

  1. git clone, etc
  2. bundle install
  3. appraisal install
  4. add --order random to the .rspec file
  5. appraisal rspec

Seeds which are known to result in errors

  • 19209 - Multiple KeyErrors
  • 5710 - Expectation failures in config_env_spec
  • 61592 - Exactly one failed test in setting the constant to use for settings
@pkuczynski
Copy link
Member

@pkuczynski pkuczynski commented Feb 8, 2018

Confirmed. I will have a look.
@pkuczynski
Copy link
Member

@pkuczynski pkuczynski commented Feb 8, 2018

If you willing to help, you are more then welcome! :)
@pkuczynski pkuczynski linked a pull request that will close this issue Jun 28, 2019
Open
@pkuczynski pkuczynski added this to the 2.3.0 milestone Mar 25, 2020
@cjlarose cjlarose self-assigned this Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cjlarose cjlarose

Labels
needs help
Milestone
3.0.0
Linked pull requests

Successfully merging a pull request may close this issue.

Execute tests in random order
3 participants
@pkuczynski @cjlarose @malakai97
You can’t perform that action at this time.