jasmine-rails 0.12.0 → 0.12.1
Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: c75716643900212d3428910021a9002e1c319b87
|
|
4
|
+
data.tar.gz: 17abc95abf0684232f5417103484d745b7425b0d
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6cfabdcf732b0a5706c02e60dfa5cf794295d53b7339d5631330d8c46297ff32f710b6c5b31fa6a3d3fd09f580835cb7e78566fdbf1969c634f301e46d043184
|
|
7
|
+
data.tar.gz: a8a816d8e833d08d980a627f47f37e87a225a7c4f50dc7e81c1821828e9c79a60e6b880d1873c1abde70972042d95894a0ff9fcff1adc32ab7dae53a3ddf1013
|
data/README.md
CHANGED
|
@@ -53,7 +53,7 @@ The jasmine-rails gem fully supports the Rails asset pipeline which means you ca
|
|
|
53
53
|
**If you choose to use the asset pipeline support, many of the `jasmine.yml`
|
|
54
54
|
configurations become unnecessary** and you can rely on the Rails asset
|
|
55
55
|
pipeline to do the hard work of controlling what files are included in
|
|
56
|
-
your
|
|
56
|
+
your test suite.
|
|
57
57
|
|
|
58
58
|
```yaml
|
|
59
59
|
# minimalist jasmine.yml configuration when leveraging asset pipeline
|
|
@@ -103,7 +103,7 @@ include_dir:
|
|
|
103
103
|
|
|
104
104
|
If you were to run:
|
|
105
105
|
|
|
106
|
-
|
|
106
|
+
bundle exec rake spec:javascript
|
|
107
107
|
|
|
108
108
|
You'd hopefully see something like:
|
|
109
109
|
|
|
@@ -113,14 +113,14 @@ You'd hopefully see something like:
|
|
|
113
113
|
|
|
114
114
|
You can filter execution by passing the `SPEC` option as well:
|
|
115
115
|
|
|
116
|
-
|
|
116
|
+
bundle exec rake spec:javascript SPEC=my_test
|
|
117
117
|
|
|
118
118
|
If you experience an error at this point, the most likely cause is JavaScript being loaded out of order, or otherwise conflicting with other existing JavaScript in your project. See "Debugging" below.
|
|
119
119
|
|
|
120
120
|
## Running from your browser
|
|
121
121
|
|
|
122
122
|
Startup your Rails server (ex: `bundle exec rails s`), and navigate to the path you have configured in your routes.rb file (ex: [http://localhost:3000/specs](http://localhost:3000/specs)).
|
|
123
|
-
The Jasmine spec runner should appear and start running your
|
|
123
|
+
The Jasmine spec runner should appear and start running your test suite instantly.
|
|
124
124
|
|
|
125
125
|
## Debugging
|
|
126
126
|
|
|
@@ -228,7 +228,7 @@ reporters:
|
|
|
228
228
|
Then, specify which reporters to use when you run the rake task:
|
|
229
229
|
|
|
230
230
|
```
|
|
231
|
-
|
|
231
|
+
REPORTERS='cool-reporter,awesome-reporter' rake spec:javascripts
|
|
232
232
|
```
|
|
233
233
|
|
|
234
234
|
The console reporter shipped with jasmine-rails will be used by
|
|
@@ -8,7 +8,8 @@ namespace :spec do
|
|
|
8
8
|
reporters = ENV.fetch('REPORTERS', 'console')
|
|
9
9
|
JasmineRails::Runner.run spec_filter, reporters
|
|
10
10
|
else
|
|
11
|
-
system(
|
|
11
|
+
system('RAILS_ENV=test bundle exec rake spec:javascript')
|
|
12
|
+
exit($?.exitstatus) if $?.exitstatus != 0
|
|
12
13
|
end
|
|
13
14
|
end
|
|
14
15
|
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: jasmine-rails
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.12.
|
|
4
|
+
version: 0.12.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Justin Searls
|
|
@@ -10,7 +10,7 @@ authors:
|
|
|
10
10
|
autorequire:
|
|
11
11
|
bindir: bin
|
|
12
12
|
cert_chain: []
|
|
13
|
-
date: 2015-09-
|
|
13
|
+
date: 2015-09-27 00:00:00.000000000 Z
|
|
14
14
|
dependencies:
|
|
15
15
|
- !ruby/object:Gem::Dependency
|
|
16
16
|
name: railties
|