Skip to content
This repository was archived by the owner on Nov 30, 2024. It is now read-only.

Make wording more accurate. #2115

Merged
merged 1 commit into from
Nov 13, 2015
Merged

Make wording more accurate. #2115

merged 1 commit into from
Nov 13, 2015

Conversation

myronmarston
Copy link
Member

The existing wording was confusing for this situation:

  • You have two specs, a and b.
  • Spec a always fails.
  • Spec b fails only if a runs first.

In such a situation, your failures are order dependent,
but our bisector printed "failure is not order dependent",
which was quite confusing. The new wording,
"failures(s) do not require any non-failures to run first"
is more accurate.

The existing wording was confusing for this situation:

* You have two specs, a and b.
* Spec a always fails.
* Spec b fails only if a runs first.

In such a situation, your failures are order dependent,
but our bisector printed "failure is not order dependent",
which was quite confusing. The new wording,
"failures(s) do not require any non-failures to run first"
is more accurate.
JonRowe added a commit that referenced this pull request Nov 13, 2015
@JonRowe JonRowe merged commit 215f149 into master Nov 13, 2015
@JonRowe JonRowe deleted the improve-bisect-wording branch November 13, 2015 12:26
@JonRowe
Copy link
Member

JonRowe commented Nov 13, 2015

👍

MatheusRich pushed a commit to MatheusRich/rspec-core that referenced this pull request Oct 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants