https://github.com/willscott/grunt-jasmine-chromeapp
Run jasmine specs in a Chrome Packaged App
https://github.com/willscott/grunt-jasmine-chromeapp
Last synced: 10 months ago
JSON representation
Run jasmine specs in a Chrome Packaged App
- Host: GitHub
- URL: https://github.com/willscott/grunt-jasmine-chromeapp
- Owner: willscott
- License: apache-2.0
- Created: 2015-01-22T21:21:37.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2017-06-20T14:54:31.000Z (almost 9 years ago)
- Last Synced: 2024-12-09T18:59:13.251Z (over 1 year ago)
- Language: JavaScript
- Size: 126 KB
- Stars: 0
- Watchers: 4
- Forks: 4
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# grunt-jasmine-chromeapp
> Run jasmine specs in a Chrome Packaged App
[](https://app.shippable.com/projects/54d3c81a5ab6cc13528afac2/builds/latest)
Getting Started
---------------
This plugin requires Grunt ```~0.4.0```
If you haven't used Grunt before, be sure to check out the Getting Started guide, which explains how to create your grunt file.
Once you're familiar with the process, this plugin can be installed as:
```shell
npm install grunt-jasmine-chromeapp --save-dev
```
Once the plugin has been installed, it may be enabled with this line of JavaScript:
```javascript
grunt.loadNpmTasks('grunt-jasmine-chromeapp');
```
Jasmine Task
------------
Run this task with the ```grunt jasmine_chromeapp``` command.
Automatically builds and maintains the spec runner and reports results back to the grunt console.
Starts chrome with a dynamically created packaged application which runs jasmine specs. The package
reports results back to a web server run by the plugin, which then reports back to the console.
This structure is chosen becasue selenium is unable to debug or instrument packaged applications
directly.
Customize your SpecRunner
-------------------------
Use your own files in the app to customize your tests.
### Options
#### src
Type: `String|Array`
Your source files and specs. These are the files you are testing.
#### options.paths
Type: `String|Array`
Listing of which files should be included as script tags in the test runner. If not set, defaults
to all files listed as source files, but can define a subset of those files to support copying
non-js files, or other support files which should not be directly included.
#### options.keepRunner
Type: `Boolean`
Default: `false`
Prevents the auto-generated app from being automatically deleted, and leave the browser open.
#### options.binary
Type: `String`
Default: `undefined`
Specify the locations of `google-chrome` to run for testing. Defaults to the [per-platform
default locations](https://code.google.com/p/selenium/wiki/ChromeDriver) specified by
chromedriver if not specified.
#### options.flags
Type: `Array`
Default: `[]`
Additional command-line flags to pass to chrome. These are appended to the default flags
used for instantiation: `--no-first-run`, `--force-app-mode`, `--apps-keep-chrome-alive-in-tests`,
`--load-and-launch-app`, and `--user-data-dir`.
`--no-startup-window` is also used for the Mac platform.
#### options.timeout
Type: `Number`
Default: `30000`
How many milliseconds to wait for the browser to start up before failing.
#### options.outfile
Type: `String`
Default: `.build`
The directory to stage the chrome app into.