add seed
This commit is contained in:
parent
e4b3335cba
commit
dcb6e10b42
11
index.md
11
index.md
@ -322,6 +322,7 @@ jasmine-headless-webkit [ -c / --colors ]
|
|||||||
[ --report <report file> ]
|
[ --report <report file> ]
|
||||||
[ --runner-out <html file> ]
|
[ --runner-out <html file> ]
|
||||||
[ -j / --jasmine-config <path to jasmine.yml> ]
|
[ -j / --jasmine-config <path to jasmine.yml> ]
|
||||||
|
[ --seed <random seed> ]
|
||||||
<spec files to run>
|
<spec files to run>
|
||||||
{% endhighlight %}
|
{% endhighlight %}
|
||||||
|
|
||||||
@ -376,6 +377,16 @@ You can also use it in your own setups, to run specs remotely and stick the resu
|
|||||||
If for some reason you're not using the default path for a `jasmine.yml` file (which is `spec/javascripts/support/jasmine.yml`),
|
If for some reason you're not using the default path for a `jasmine.yml` file (which is `spec/javascripts/support/jasmine.yml`),
|
||||||
you can provide that path with `-j`.
|
you can provide that path with `-j`.
|
||||||
|
|
||||||
|
### Randomizing the order of spec files
|
||||||
|
|
||||||
|
Spec files are shuffled into a random order before each run. This lets you find issues where spec files may depend on state
|
||||||
|
established in prior executed spec files -- a bad thing. After each run, you'll get the random seed used to randomize the files:
|
||||||
|
|
||||||
|
`Test random seed: --seed 1234`
|
||||||
|
|
||||||
|
If you're getting weird results related to the particula order of a run of specs, pass that same seed value back in
|
||||||
|
and get to work!
|
||||||
|
|
||||||
### Running only certain spec files
|
### Running only certain spec files
|
||||||
|
|
||||||
By default, if no files are passed into `jasmine-headless-webkit`, all possible spec files in the `spec_files` definition
|
By default, if no files are passed into `jasmine-headless-webkit`, all possible spec files in the `spec_files` definition
|
||||||
|
Loading…
Reference in New Issue
Block a user