9
82%
master: 81%

Ran 16 Sep 2013 05:32AM UTC

Files 11

Run time –

Badge

Embed ▾

Committed 16 Sep 2013 05:26AM UTC coverage: 96.137%. Remained the same

Job # 2.0.0

Build Type

push

travis-ci

Committed by

myronmarston

Commit Message

Remove inconsistent #order and #randomize? config methods.

* Examples and groups can be ordered differently.
* Individual groups can be ordered differently.

As such, a global `order` reader method doesn't
make a lot of sense (although, assigning the global
default via `#order=` still does, I think).

Also:

* This exposed that the ordering force logic
  (e.g. to ensure CLI `--order rand` takes
  precedence over `RSpec.configure`) didn't
  work properly since it simply ensured `order`
  returned the forced option but did not ensure
  the global ordering was set properly.  I've
  fixed this.
* Don't clear the seed when setting the order to
  default. An individual example group may still
  be run in random order and will need the seed.
  There's really no reason to clear it.
* Base our decision of whether or not to print
  the seed at the end of the run on whether or
  not the random strategy ever got used, rather
  than whether or not `random` is the global
  strategy. If only one example group used the
  random strategy we would want it to print,
  but the old logic would not have done so.

Run Details

448 of 466 relevant lines covered (96.14%)

21.49 hits per line

rspec / rspec-core / 1773 / 9
82%
master: 81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1773.9 (2.0.0)

rspec / rspec-core / 1773 / 9 82% master: 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1773.9 (2.0.0)

rspec / rspec-core / 1773 / 9
82%
master: 81%

README BADGES
x