Jasmine is a behavior-driven development framework for testing JavaScript code. It does not depend on any other JavaScript frameworks. It does not require a DOM. And it has a clean, obvious syntax so that you can easily write tests. This package is for Jasmine version 2.0.0.
To install through Package Control, search for Jasmine. If you still don't have Package Control in Sublime Text, go get it. If you insist to not install it, you can download the package and put it manually inside your Pacakages directory. It should work but will not update automatically.
Some of the snippets in the wild.
Below is a list of all snippets currently supported on this package and the
triggers of each one. The ⇥ means the TAB key.
describe: desc⇥xdescribe: xdesc⇥it: it⇥xit: xit⇥afterEach: ae⇥beforeEach: be⇥
expect: exp⇥expect().toBe: tb⇥expect().toBeCloseTo: tbct⇥expect().toBeDefined: tbd⇥expect().toBeFalsy: tbf⇥expect().toBeGreaterThan: tbgt⇥expect().toBeLessThan: tblt⇥expect().toBeNull: tbn⇥expect().toBeTruthy: tbt⇥expect().toBeUndefined: tbu⇥expect().toContain: tc⇥expect().toEqual: te⇥expect().toHaveBeenCalled: thbc⇥expect().toHaveBeenCalledWith: thbcw⇥expect().toMatch: tm⇥expect().toThrow: tt⇥expect().not.toBe: nb⇥expect().not.toBeCloseTo: nct⇥expect().not.toBeDefined: nd⇥expect().not.toBeFalsy: nf⇥expect().not.toBeGreaterThan: ngt⇥expect().not.toBeLessThan: nlt⇥expect().not.toBeNull: nn⇥expect().not.toBeTruthy: nt⇥expect().not.toBeUndefined: nu⇥expect().not.toContain: nc⇥expect().not.toEqual: ne⇥expect().not.toMatch: nm⇥expect().not.toThrow: nt⇥jasmine.any: a⇥jasmine.objectContaining: oc⇥
spyOn: s⇥spyOn.and.callThrough: sct⇥spyOn.and.returnValue: srv⇥spyOn.and.stub: ss⇥spyOn.and.throwError: se⇥spy.calls.all: ca⇥spy.calls.allArgs: caa⇥spy.calls.any: ca⇥spy.calls.argsFor: caf⇥spy.calls.count: cc⇥spy.calls.first: cf⇥spy.calls.mostRecent: cmr⇥spy.calls.reset: cr⇥createSpy: cs⇥createSpyObj: cso⇥
This command will open the spec or source file that has the same path of the active view file. If you're looking at a source file and the package can't find any specs, it'll display a list of possible directories to create a new one.
To run this command, you can use ctrl+. or ctrl+shift+. (this last one will
toggle using a split view), or select Jasmine BDD: Switch between code and spec.
This command is exactly the same as running toggle and not finding specs. It
doesn't have a key binding, but you can use jasmine_create_spec as a command
name, like this:
{ "keys": ["KEYS"], "command": "jasmine_create_spec", "args": { "split_view": false } }
There are two possible settings:
{
// Ignore directories when searching for files (source and specs)
"ignored_directories": [".git", "vendor", "tmp", "node_modules"],
// The parent folder name for the spec files
"jasmine_path": "spec"
}- Fork this repository
- Run
npm install - Create a new branch for each feature or improvement
- Ensure that your code is accompanied with tests
- Run
grunt testto ensure that your new tests and the old ones are all passing - Send a pull request from each feature branch
If you're on a OS X machine, you can run npm run-script symlink to symlink
this package directly to
~/Library/Application\ Support/Sublime\ Text\ 3/Packages/jasmine-snippets
and see the changes everytime you save a file.
The MIT License (MIT)
Copyright (c) 2014 Caio Gondim
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.