GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
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".
Aliasing specify() to it()
Running 'rake spec' changes
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.
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
@env.specify = @env.it
@specify = @it