Aliasing specify() to it() #166

Closed
wants to merge 2 commits into
from

Conversation

Projects
None yet
3 participants

There are times when the code just reads better with the "specify" function name.

Here is an example: specify("the first element is pulled") reads much better than it("the first element is pulled").

I have 2 commits in this pull request. The first one is the aliasing change and the second one is the modified files after I ran "rake spec".

Contributor

infews commented Jan 8, 2012

Thanks for this work and idea. But we're not going to pull this request.

We don't want to extend the interface of Jasmine except when explicitly required. This aliasing can be done in a helper function - run once per suite - and thus any project can pick their verbs.

@infews infews closed this Jan 8, 2012

Contributor

thedeeno commented Feb 25, 2012

hmm, I don't get how to do this in a helper. What should I be hooking the aliases onto? The following hasn't worked for me (coffeescript):

[global].specify = jasmine.getEnv().it

# or

beforeEach ->
  @env.specify = @env.it
  # or
  @specify = @it

Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment