A Grunt task to make Jasmine testing on Ext.js and Sencha Touch projects easier. It extends the
grunt-contrib-jasminetask and so therefore any of the options available on that task also work here.
This plugin requires Grunt
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-sencha-jasmine --save-dev
This task extends the
grunt-contrib-jasmine task and just provides a simpler way of getting an Ext.js and Sencha Touch project running Jasmine tasks.
Please refer to the [https://github.com/gruntjs/grunt-contrib-jasmine] docs for more details. This page will only cover the specifics for working with Ext.js.
In your project's Gruntfile, add a section named
sencha_jasmine to the data object passed into
Reminder that this task extends the
grunt-contrib-jasmine task and therefore all the options they support are also supported.
This is the only required property and should point to the directory in which Ext.js is installed.
Use this to set the Ext.Loader paths to point your namespaces to the correct locations. The namespaces should be relative to the root directory of your ptoject which is where the
_SpecRunner.html is generated. If you're running the task against a remote server you should make sure the paths are correct for that page on the server. In the generated
_SpecRunner.html this will be used to call:
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.
0.2.4 Updating to grunt-contrib-jasmine 0.5.2 by default
0.2.3 Fixed bugs #1 and #2
0.2.0 Add support for the
extLoaderPaths config property and fix bug whereby only a locally installed grunt-contrib-jasmine would get picked up.
0.1.0 First release which supports the