Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Execute specs in random order #583

Closed
demisx opened this Issue · 5 comments

4 participants

@demisx

Hi. Is it possible to force specs execute in random order, similar to RSpec? That would help to detect interdependencies between the specs early.

Thanks.

@infews
Owner

Not directly at the moment. But many have asked for this.

We have a feature coming that would enable all sorts of fun things regarding which specs are run and in which order. You can follow this story in our backlog.

Closing.

@infews infews closed this
@demisx

FYI, couldn't follow that story. The "Follow story" checkbox is disabled for my login.

@sdemjanenko

Has any progress been made on this front?

@slackersoft
Owner

The current way to run your specs in a random order is to call Env.execute and pass in a list of spec or suite ids in the order you want the specs to run. When we first started implementing beforeAll and afterAll we consciously broke this functionality until we could figure out how we wanted to handle arbitrary ordering with the Alls. We made sure not to release Jasmine in a state where passing an order to execute didn't work, but doing so made Alls behave like Eachs. This has been changed on master, and they should behave as expected going forward.

@sdemjanenko

Couldn't modifying the TreeProcessor achieve this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.