jasmine 2.0.0.rc5 → 2.0.0

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: 3a7ce607ec6c8a6bb64af21d08f21d8305dceb95
4
+ data.tar.gz: c86fcfa19f64ff33754b2fd6251d1d4c8abc9073
5
+ SHA512:
6
+ metadata.gz: d0013fece64deeb497579113f9004c4765a1040b6cd5b076c8876bde288488f2a08a0505df12f75bb7e1b48cbb4eb6deec0984c2dde5bfb8ef175a0c7d5abf86
7
+ data.tar.gz: e613e70b7b99fd68da008e3f2ae2bba56cc145df85ae9c8053b4bdb062d7324562e9f6bd1561e85288122345a9cf7cecb66782717af663c54122a254a1aed4ec
@@ -4,7 +4,7 @@ rvm:
4
4
  - "1.9.3"
5
5
  - "2.0.0"
6
6
  - "jruby"
7
- - "rbx-19mode"
7
+ - "rbx-2"
8
8
 
9
9
  env:
10
10
  - "RAILS_VERSION=rails3"
data/Gemfile CHANGED
@@ -22,3 +22,9 @@ if ENV['RAILS_VERSION'] == "rails3"
22
22
  else
23
23
  gem 'rack', '1.5.2'
24
24
  end
25
+
26
+ platform :rbx do
27
+ gem 'json'
28
+ gem 'rubysl'
29
+ gem 'racc'
30
+ end
@@ -1,4 +1,4 @@
1
- # The Jasmine Gem <a title="Build at Travis CI" href="http://travis-ci.org/#!/pivotal/jasmine-gem"><img src="https://secure.travis-ci.org/pivotal/jasmine-gem.png" /></a>
1
+ # The Jasmine Gem [![Build Status](https://travis-ci.org/pivotal/jasmine-gem.png?branch=master)](https://travis-ci.org/pivotal/jasmine-gem)
2
2
 
3
3
  The [Jasmine](http://github.com/pivotal/jasmine) Ruby Gem is a package of helper code for developing Jasmine projects for Ruby-based web projects (Rails, Sinatra, etc.) or for JavaScript projects where Ruby is a welcome partner. It serves up a project's Jasmine suite in a browser so you can focus on your code instead of manually editing script tags in the Jasmine runner HTML file.
4
4
 
@@ -27,20 +27,25 @@ To initialize a project for Jasmine
27
27
  For any other project (Sinatra, Merb, or something we don't yet know about) use
28
28
 
29
29
  `jasmine init`
30
+ `jasmine examples`
30
31
 
31
32
  ## Usage
32
33
 
33
34
  Start the Jasmine server:
34
35
 
35
- `rake jasmine`
36
+ rake jasmine
36
37
 
37
38
  Point your browser to `localhost:8888`. The suite will run every time this page is re-loaded.
38
39
 
39
40
  For Continuous Integration environments, add this task to the project build steps:
40
41
 
41
- `rake jasmine:ci`
42
+ rake jasmine:ci
42
43
 
43
- This uses PhantomJS to load and run the Jasmine suite.
44
+ This uses PhantomJS to load and run the Jasmine suite.
45
+
46
+ Please note that PhantomJS will be auto-installed by the [phantomjs-gem][phantomjs-gem] at the first `rake jasmine:ci` run. If you have a PhantomJS somewhere on your path, it won't install.
47
+
48
+ [phantomjs-gem]: https://github.com/colszowka/phantomjs-gem#phantomjs-as-a-rubygem
44
49
 
45
50
  ## Configuration
46
51
 
@@ -52,7 +57,7 @@ Alternatively, you may specify the path to your `jasmine.yml` by setting an envi
52
57
  `rake jasmine:ci JASMINE_CONFIG_PATH=relative/path/to/your/jasmine.yml`
53
58
 
54
59
  In addition, the `spec_helper` key in your jasmine.yml specifies the path to a ruby file that can do programmatic configuration.
55
- After running `jasmine init` or `rails g jasmine:init` it will point to `spec/javascripts/support/jasmine_helper.rb` which you can modify to fit your needs.
60
+ After running `jasmine init` or `rails g jasmine:install` it will point to `spec/javascripts/support/jasmine_helper.rb` which you can modify to fit your needs.
56
61
 
57
62
  ### Running Jasmine on a different port
58
63
 
@@ -1,7 +1,5 @@
1
1
  # Releasing Jasmine
2
2
 
3
- Add release notes to gh-pages branch /release-notes.html.markdown
4
-
5
3
  ## Jasmine core
6
4
 
7
5
  See release docs in jasmine-core
@@ -12,5 +10,6 @@ See release docs in jasmine-core
12
10
  1. update version in version.rb
13
11
  * for release candidates, add ".rc" + number to the end of the appropriate version part
14
12
  1. commit and push the version update to github
13
+ 1. Update the gemspec to depend on the latest version of jasmine-core
15
14
  1. `rake release` - tags the repo with the version, builds the `jasmine` gem, pushes the gem to Rubygems.org. In order to release you will have to ensure you have rubygems creds locally.
16
15
 
@@ -31,8 +31,9 @@ Gem::Specification.new do |s|
31
31
  s.add_development_dependency 'rack-test'
32
32
  s.add_development_dependency 'multi_json'
33
33
  s.add_development_dependency 'rspec', '>= 2.5.0'
34
+ s.add_development_dependency 'nokogiri'
34
35
 
35
- s.add_dependency 'jasmine-core', '~> 2.0.0.rc5'
36
+ s.add_dependency 'jasmine-core', '~> 2.0.0'
36
37
  s.add_dependency 'rack', '>= 1.2.1'
37
38
  s.add_dependency 'rake'
38
39
  s.add_dependency 'phantomjs'
@@ -23,7 +23,9 @@ module Jasmine
23
23
  end
24
24
 
25
25
  def use_asset_pipeline?
26
- (rails3? || rails4?) && Rails.respond_to?(:application) && Rails.application.respond_to?(:assets)
26
+ assets_pipeline_available = (rails3? || rails4?) && Rails.respond_to?(:application) && Rails.application.respond_to?(:assets)
27
+ rails3_assets_enabled = rails3? && assets_pipeline_available && Rails.application.config.assets.enabled != false
28
+ assets_pipeline_available && (rails4? || rails3_assets_enabled)
27
29
  end
28
30
 
29
31
  private
@@ -1,3 +1,3 @@
1
1
  module Jasmine
2
- VERSION = "2.0.0.rc5"
2
+ VERSION = "2.0.0"
3
3
  end
@@ -1,6 +1,6 @@
1
1
  # Jasmine Gem 2.0 Release Notes
2
2
 
3
- These notes cover version 2.0.0.rc4
3
+ These notes cover version 2.0.0
4
4
 
5
5
  ## Summary
6
6
 
@@ -15,7 +15,7 @@ The default Runner uses PhantomJS to run the suite. The default Formatter sends
15
15
  ## Dropped Support
16
16
 
17
17
  * _Most_ ENV variables removed - use `Jasmine.configure` to set browser, ports, etc.
18
- * Dropped support for 1.8.x Rubies, Rails 2, RSpec 1 - please continue to use Jasmine gem 1.3.2
18
+ * Dropped support for 1.8.x Rubies, Rails 2, RSpec 1, 1.9 rbx - please continue to use Jasmine gem 1.3.2
19
19
  * "self-test" is gone as [Jasmine core now tests itself](http://travis-ci.org/pivotal/jasmine)
20
20
 
21
21
  ## Changes
@@ -37,23 +37,15 @@ The default Runner uses PhantomJS to run the suite. The default Formatter sends
37
37
  * Improved integration tests with Rails
38
38
  * Added the configuration option to specify your own Webdriver instance
39
39
  * Brought back the Jasmine Favicon
40
+ * Better re-work of Runners and Formatters
41
+ * User can copy `boot.js` into their project for customization - usage: `jasmine copy_boot_js`
40
42
 
41
- ### In RC4
43
+ ### Fixes
42
44
 
45
+ * Update template jasmine.yml to include boot_dir and boot_files
43
46
  * `jasmine:ci` rake task doesn't call exit and stop other rake tasks
44
-
45
47
  * Respect source js files outside the asset pipeline
46
-
47
- [Finish #37284657](http://www.pivotaltracker.com/story/37284657)
48
- * SHA: ad8f6c839bce5d362409e59c46043b0ecc762faf
49
- * Gregg Van Hove and Tim Jarratt, pair+gvanhove+tjarratt@pivotallabs.com
50
-
51
-
52
- ### In RC3
53
-
54
- * Better re-work of Runners and Formatters
55
48
  * In Rails 4, turn off turbolink processing of jasmine runner spec links so spec links work
56
- * User can copy `boot.js` into their project for customization - usage: `jasmine copy_boot_js`
57
49
  * Allow user to configure path to `jasmine.yml` via an ENV variable.
58
50
  * More data printed out to console when starting the Jasmine server
59
51
  * Support for specs to be written in CoffeeScript when used with Rails
@@ -65,6 +57,8 @@ The default Runner uses PhantomJS to run the suite. The default Formatter sends
65
57
  * Extraction to separate gems for:
66
58
  * JUnit XML formatter
67
59
  * Selenium/Webdriver integration
60
+ * Use IE=edge for IE compatibility because this will put IE into the highest available mode for each version of IE - see [Question on StackOverflow](http://stackoverflow.com/questions/3449286/force-ie-compatibility-mode-off-in-ie-using-tags) - #[168](http://github.com/pivotal/jasmine-gem/pull/168) from @iwz
61
+
68
62
 
69
63
  ## Accepted Pull Requests
70
64
 
@@ -74,12 +68,7 @@ The default Runner uses PhantomJS to run the suite. The default Formatter sends
74
68
  * Remove unused code - #[154](http://github.com/pivotal/jasmine-gem/pull/154) from @daytonn
75
69
  * Fix default path for :spec_helper in template #[147](http://github.com/pivotal/jasmine-gem/pull/147) from @kmayer
76
70
  * Improve Gemfile installation instructions #[141](http://github.com/pivotal/jasmine-gem/pull/141)
77
-
78
- ### In RC3
79
-
80
- * Use IE=edge for IE compatibility because this will put IE into the highest available mode for each version of IE - see [Question on StackOverflow](http://stackoverflow.com/questions/3449286/force-ie-compatibility-mode-off-in-ie-using-tags
81
- ) - #[168](http://github.com/pivotal/jasmine-gem/pull/168) from @iwz
82
-
71
+ * Fix issue when using Rails 4 without the asset pipeline from @lukeasrodgers
83
72
 
84
73
  ------
85
74
 
@@ -29,6 +29,8 @@ if Jasmine::Dependencies.rails_available?
29
29
  open('Gemfile', 'a') { |f|
30
30
  f.puts "gem 'jasmine', :path => '#{base}'"
31
31
  f.puts "gem 'jasmine-core', :github => 'pivotal/jasmine'"
32
+ f.puts "gem 'rubysl', :platform => :rbx"
33
+ f.puts "gem 'racc', :platform => :rbx"
32
34
  f.flush
33
35
  }
34
36
 
metadata CHANGED
@@ -1,8 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: jasmine
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.0.rc5
5
- prerelease: 6
4
+ version: 2.0.0
6
5
  platform: ruby
7
6
  authors:
8
7
  - Rajan Agaskar
@@ -11,134 +10,132 @@ authors:
11
10
  autorequire:
12
11
  bindir: bin
13
12
  cert_chain: []
14
- date: 2013-10-30 00:00:00.000000000 Z
13
+ date: 2013-12-17 00:00:00.000000000 Z
15
14
  dependencies:
16
15
  - !ruby/object:Gem::Dependency
17
16
  name: rails
18
17
  requirement: !ruby/object:Gem::Requirement
19
- none: false
20
18
  requirements:
21
- - - ! '>='
19
+ - - '>='
22
20
  - !ruby/object:Gem::Version
23
21
  version: '4'
24
22
  type: :development
25
23
  prerelease: false
26
24
  version_requirements: !ruby/object:Gem::Requirement
27
- none: false
28
25
  requirements:
29
- - - ! '>='
26
+ - - '>='
30
27
  - !ruby/object:Gem::Version
31
28
  version: '4'
32
29
  - !ruby/object:Gem::Dependency
33
30
  name: rack-test
34
31
  requirement: !ruby/object:Gem::Requirement
35
- none: false
36
32
  requirements:
37
- - - ! '>='
33
+ - - '>='
38
34
  - !ruby/object:Gem::Version
39
35
  version: '0'
40
36
  type: :development
41
37
  prerelease: false
42
38
  version_requirements: !ruby/object:Gem::Requirement
43
- none: false
44
39
  requirements:
45
- - - ! '>='
40
+ - - '>='
46
41
  - !ruby/object:Gem::Version
47
42
  version: '0'
48
43
  - !ruby/object:Gem::Dependency
49
44
  name: multi_json
50
45
  requirement: !ruby/object:Gem::Requirement
51
- none: false
52
46
  requirements:
53
- - - ! '>='
47
+ - - '>='
54
48
  - !ruby/object:Gem::Version
55
49
  version: '0'
56
50
  type: :development
57
51
  prerelease: false
58
52
  version_requirements: !ruby/object:Gem::Requirement
59
- none: false
60
53
  requirements:
61
- - - ! '>='
54
+ - - '>='
62
55
  - !ruby/object:Gem::Version
63
56
  version: '0'
64
57
  - !ruby/object:Gem::Dependency
65
58
  name: rspec
66
59
  requirement: !ruby/object:Gem::Requirement
67
- none: false
68
60
  requirements:
69
- - - ! '>='
61
+ - - '>='
70
62
  - !ruby/object:Gem::Version
71
63
  version: 2.5.0
72
64
  type: :development
73
65
  prerelease: false
74
66
  version_requirements: !ruby/object:Gem::Requirement
75
- none: false
76
67
  requirements:
77
- - - ! '>='
68
+ - - '>='
78
69
  - !ruby/object:Gem::Version
79
70
  version: 2.5.0
71
+ - !ruby/object:Gem::Dependency
72
+ name: nokogiri
73
+ requirement: !ruby/object:Gem::Requirement
74
+ requirements:
75
+ - - '>='
76
+ - !ruby/object:Gem::Version
77
+ version: '0'
78
+ type: :development
79
+ prerelease: false
80
+ version_requirements: !ruby/object:Gem::Requirement
81
+ requirements:
82
+ - - '>='
83
+ - !ruby/object:Gem::Version
84
+ version: '0'
80
85
  - !ruby/object:Gem::Dependency
81
86
  name: jasmine-core
82
87
  requirement: !ruby/object:Gem::Requirement
83
- none: false
84
88
  requirements:
85
89
  - - ~>
86
90
  - !ruby/object:Gem::Version
87
- version: 2.0.0.rc5
91
+ version: 2.0.0
88
92
  type: :runtime
89
93
  prerelease: false
90
94
  version_requirements: !ruby/object:Gem::Requirement
91
- none: false
92
95
  requirements:
93
96
  - - ~>
94
97
  - !ruby/object:Gem::Version
95
- version: 2.0.0.rc5
98
+ version: 2.0.0
96
99
  - !ruby/object:Gem::Dependency
97
100
  name: rack
98
101
  requirement: !ruby/object:Gem::Requirement
99
- none: false
100
102
  requirements:
101
- - - ! '>='
103
+ - - '>='
102
104
  - !ruby/object:Gem::Version
103
105
  version: 1.2.1
104
106
  type: :runtime
105
107
  prerelease: false
106
108
  version_requirements: !ruby/object:Gem::Requirement
107
- none: false
108
109
  requirements:
109
- - - ! '>='
110
+ - - '>='
110
111
  - !ruby/object:Gem::Version
111
112
  version: 1.2.1
112
113
  - !ruby/object:Gem::Dependency
113
114
  name: rake
114
115
  requirement: !ruby/object:Gem::Requirement
115
- none: false
116
116
  requirements:
117
- - - ! '>='
117
+ - - '>='
118
118
  - !ruby/object:Gem::Version
119
119
  version: '0'
120
120
  type: :runtime
121
121
  prerelease: false
122
122
  version_requirements: !ruby/object:Gem::Requirement
123
- none: false
124
123
  requirements:
125
- - - ! '>='
124
+ - - '>='
126
125
  - !ruby/object:Gem::Version
127
126
  version: '0'
128
127
  - !ruby/object:Gem::Dependency
129
128
  name: phantomjs
130
129
  requirement: !ruby/object:Gem::Requirement
131
- none: false
132
130
  requirements:
133
- - - ! '>='
131
+ - - '>='
134
132
  - !ruby/object:Gem::Version
135
133
  version: '0'
136
134
  type: :runtime
137
135
  prerelease: false
138
136
  version_requirements: !ruby/object:Gem::Requirement
139
- none: false
140
137
  requirements:
141
- - - ! '>='
138
+ - - '>='
142
139
  - !ruby/object:Gem::Version
143
140
  version: '0'
144
141
  description: Test your JavaScript without any framework dependencies, in any environment,
@@ -204,10 +201,7 @@ files:
204
201
  - lib/rack/jasmine/runner.rb
205
202
  - release_notes/v1.2.1.md
206
203
  - release_notes/v1.3.2.md
207
- - release_notes/v2.0.0.rc2.md
208
- - release_notes/v2.0.0.rc3.md
209
- - release_notes/v2.0.0.rc4.md
210
- - release_notes/v2.0.0.rc5.md
204
+ - release_notes/v2.0.0.md
211
205
  - spec/application_integration_spec.rb
212
206
  - spec/application_spec.rb
213
207
  - spec/base_spec.rb
@@ -236,28 +230,27 @@ files:
236
230
  homepage: http://pivotal.github.com/jasmine/
237
231
  licenses:
238
232
  - MIT
233
+ metadata: {}
239
234
  post_install_message:
240
235
  rdoc_options:
241
236
  - --charset=UTF-8
242
237
  require_paths:
243
238
  - lib
244
239
  required_ruby_version: !ruby/object:Gem::Requirement
245
- none: false
246
240
  requirements:
247
- - - ! '>='
241
+ - - '>='
248
242
  - !ruby/object:Gem::Version
249
243
  version: '0'
250
244
  required_rubygems_version: !ruby/object:Gem::Requirement
251
- none: false
252
245
  requirements:
253
- - - ! '>'
246
+ - - '>='
254
247
  - !ruby/object:Gem::Version
255
- version: 1.3.1
248
+ version: '0'
256
249
  requirements: []
257
250
  rubyforge_project:
258
- rubygems_version: 1.8.25
251
+ rubygems_version: 2.0.6
259
252
  signing_key:
260
- specification_version: 3
253
+ specification_version: 4
261
254
  summary: JavaScript BDD framework
262
255
  test_files:
263
256
  - spec/application_integration_spec.rb
@@ -1,44 +0,0 @@
1
- # Jasmine Gem 2.0 Release Notes
2
-
3
- ## Summary
4
-
5
- These notes cover v2.0.0.rc2.
6
-
7
- ## Changes
8
-
9
- * Support for changes in Jasmine 2.0
10
- * hooks for `boot_dir` and `boot_files`
11
- * New resutls interface in reporters
12
- * Results Formatters
13
- * New console results formatter for CI tasks - no longer depend on RSpec for console output
14
- * Optional JUnit XML results formatter for CI tasks
15
- * Projects can provide custom formatters
16
- * Rails 4 support
17
- * Better support for non-Rails Ruby projects
18
- * Loosely pinning to jasmine-core, allowing for jasmine-core's build to work on release for jasmine build to work.
19
- * SHA: 42021e3a86e57f6b7b23dfbe921867d7560f4e4f
20
- * Add warning to jasmine init
21
- * SHA: e071474b014e7d6909d69f86988b84eacb801201
22
- * Globbing should now return files in a consistent, predictable order across systems
23
- * Reactivated the Rails integration tests; fix resulting issues
24
- * Added the configuration option to specify your own webdriver instance
25
- * Brought back the Jasmine Favicon
26
-
27
- ## Dropped Support
28
-
29
- * ENV variables removed - use Jasmine.configure to set browser, ports, etc.
30
- * Dropped support for 1.8.x Rubies, Rails 2, RSpec 1 - please continue to use Jasmine gem 1.3.2
31
- * "self-test" is gone as [Jasmine core now tests itself](http://travis-ci.org/pivotal/jasmine)
32
-
33
- ## Pull Requests
34
-
35
- * Fix README.markdown and add config example #[144](http://github.com/pivotal/jasmine-gem/pull/144) from enrapt-mochizuki
36
- * Use a relative path to jasmine repo in Gemfile #[161](http://github.com/pivotal/jasmine-gem/pull/161) from zephyr-dev
37
- * Problem when using a asset prefix other than '/assets' #[155](http://github.com/pivotal/jasmine-gem/pull/155) from janv
38
- * Remove unused code - #[154]((http://github.com/pivotal/jasmine-gem/pull/154) from daytonn
39
- * Fix default path for :spec_helper in template #[147]((http://github.com/pivotal/jasmine-gem/pull/147) from kmayer
40
- * Improve Gemfile installation instructions #[141]((http://github.com/pivotal/jasmine-gem/pull/141)
41
-
42
- ------
43
-
44
- _Release Notes generated with [Anchorman](http://github.com/infews/anchorman)_
@@ -1,78 +0,0 @@
1
- # Jasmine Gem 2.0 Release Notes
2
-
3
- These notes cover version 2.0.0.rc3
4
-
5
- ## Summary
6
-
7
- This release is focused on support for Jasmine 2.0, gem configuration simplification, and improvement of Rails support (including Rails 4).
8
-
9
- The `Jasmine.configure` block now allows for fine-tuned configuration of how a project's suite is run. There are two new/refined concepts: Runners and Formatters.
10
-
11
- Formatters are responsible for taking the results from the Jasmine suite and presenting the data in a specific format. Runners take a URL and a Formatter and are responsible for running the Jasmine suite and passing results to the given formatter.
12
-
13
- The default Runner uses PhantomJS to run the suite. The default Formatter sends results to the console. There are Ruby gems for a [Selenium/Webdriver Runner][selenium] and a [JUnit XML Formatter][junit]. These projects are great examples for writing a Runner or Formatter for your environment.
14
-
15
- ## Dropped Support
16
-
17
- * _Most_ ENV variables removed - use `Jasmine.configure` to set browser, ports, etc.
18
- * Dropped support for 1.8.x Rubies, Rails 2, RSpec 1 - please continue to use Jasmine gem 1.3.2
19
- * "self-test" is gone as [Jasmine core now tests itself](http://travis-ci.org/pivotal/jasmine)
20
-
21
- ## Changes
22
-
23
- * Support for changes in Jasmine 2.0
24
- * Hooks in `jasmine.yml` and configuration for `boot_dir` and `boot_files`
25
- * Support for changes to results interface
26
- * Results Formatters:
27
- * New console results formatter for CI tasks - Jasmine Gem no longer depend on RSpec for console output
28
- * Optional JUnit XML results formatter for CI tasks
29
- * Projects can provide custom formatters
30
- * Rails 4 support
31
- * Better support for non-Rails Ruby projects
32
- * Loosely pinning to the `jasmine-core` gem, allowing for Jasmine Core's build to work on release for Jasmine build to work.
33
- * SHA: 42021e3a86e57f6b7b23dfbe921867d7560f4e4f
34
- * Add warning to `jasmine init`
35
- * SHA: e071474b014e7d6909d69f86988b84eacb801201
36
- * Globbing should now return files in a consistent, predictable order across systems
37
- * Improved integration tests with Rails
38
- * Added the configuration option to specify your own Webdriver instance
39
- * Brought back the Jasmine Favicon
40
-
41
- ### In RC3
42
-
43
- * Better re-work of Runners and Formatters
44
- * In Rails 4, turn off turbolink processing of jasmine runner spec links so spec links work
45
- * User can copy `boot.js` into their project for customization - usage: `jasmine copy_boot_js`
46
- * Allow user to configure path to `jasmine.yml` via an ENV variable.
47
- * More data printed out to console when starting the Jasmine server
48
- * Support for specs to be written in CoffeeScript when used with Rails
49
- * Fix stylesheet asset expansion for Rails 4
50
- * Remove RSpec dependency - Jasmine gem builds its own output
51
- * Remove Selenium dependency - builds run against PhantomJS by default
52
- * Remove accidental sqllite development dependency
53
- * Jasmine example code no longer installed when `jasmine init` is run. Examples are now installed explicitly with `jasmine examples`
54
- * Extraction to separate gems for:
55
- * JUnit XML formatter
56
- * Selenium/Webdriver integration
57
-
58
- ## Accepted Pull Requests
59
-
60
- * Fix README.markdown and add config example #[144](http://github.com/pivotal/jasmine-gem/pull/144) from @enrapt-mochizuki
61
- * Use a relative path to jasmine repo in Gemfile #[161](http://github.com/pivotal/jasmine-gem/pull/161) from @zephyr-dev
62
- * Problem when using a asset prefix other than '/assets' #[155](http://github.com/pivotal/jasmine-gem/pull/155) from @janv
63
- * Remove unused code - #[154](http://github.com/pivotal/jasmine-gem/pull/154) from @daytonn
64
- * Fix default path for :spec_helper in template #[147](http://github.com/pivotal/jasmine-gem/pull/147) from @kmayer
65
- * Improve Gemfile installation instructions #[141](http://github.com/pivotal/jasmine-gem/pull/141)
66
-
67
- ### In RC3
68
-
69
- * Use IE=edge for IE compatibility because this will put IE into the highest available mode for each version of IE - see [Question on StackOverflow](http://stackoverflow.com/questions/3449286/force-ie-compatibility-mode-off-in-ie-using-tags
70
- ) - #[168](http://github.com/pivotal/jasmine-gem/pull/168) from @iwz
71
-
72
-
73
- ------
74
-
75
- _Release Notes generated with [Anchorman](http://github.com/infews/anchorman)_
76
-
77
- [selenium]: https://github.com/jasmine/jasmine_selenium_runner
78
- [junit]: https://github.com/jasmine/jasmine_junitxml_formatter
@@ -1,94 +0,0 @@
1
- # Jasmine Gem 2.0 Release Notes
2
-
3
- These notes cover version 2.0.0.rc5
4
-
5
- ## Summary
6
-
7
- This release is focused on support for Jasmine 2.0, gem configuration simplification, and improvement of Rails support (including Rails 4).
8
-
9
- The `Jasmine.configure` block now allows for fine-tuned configuration of how a project's suite is run. There are two new/refined concepts: Runners and Formatters.
10
-
11
- Formatters are responsible for taking the results from the Jasmine suite and presenting the data in a specific format. Runners take a URL and a Formatter and are responsible for running the Jasmine suite and passing results to the given formatter.
12
-
13
- The default Runner uses PhantomJS to run the suite. The default Formatter sends results to the console. There are Ruby gems for a [Selenium/Webdriver Runner][selenium] and a [JUnit XML Formatter][junit]. These projects are great examples for writing a Runner or Formatter for your environment.
14
-
15
- ## Dropped Support
16
-
17
- * _Most_ ENV variables removed - use `Jasmine.configure` to set browser, ports, etc.
18
- * Dropped support for 1.8.x Rubies, Rails 2, RSpec 1 - please continue to use Jasmine gem 1.3.2
19
- * "self-test" is gone as [Jasmine core now tests itself](http://travis-ci.org/pivotal/jasmine)
20
-
21
- ## Changes
22
-
23
- * Support for changes in Jasmine 2.0
24
- * Hooks in `jasmine.yml` and configuration for `boot_dir` and `boot_files`
25
- * Support for changes to results interface
26
- * Results Formatters:
27
- * New console results formatter for CI tasks - Jasmine Gem no longer depend on RSpec for console output
28
- * Optional JUnit XML results formatter for CI tasks
29
- * Projects can provide custom formatters
30
- * Rails 4 support
31
- * Better support for non-Rails Ruby projects
32
- * Loosely pinning to the `jasmine-core` gem, allowing for Jasmine Core's build to work on release for Jasmine build to work.
33
- * SHA: 42021e3a86e57f6b7b23dfbe921867d7560f4e4f
34
- * Add warning to `jasmine init`
35
- * SHA: e071474b014e7d6909d69f86988b84eacb801201
36
- * Globbing should now return files in a consistent, predictable order across systems
37
- * Improved integration tests with Rails
38
- * Added the configuration option to specify your own Webdriver instance
39
- * Brought back the Jasmine Favicon
40
-
41
- ### In RC5
42
-
43
- * Update SpecHelper template from latest jasmine-core template to show how to add custom matchers
44
- * Update template jasmine.yml to include boot_dir and boot_files
45
-
46
- ### In RC4
47
-
48
- * `jasmine:ci` rake task doesn't call exit and stop other rake tasks
49
-
50
- * Respect source js files outside the asset pipeline
51
-
52
- [Finish #37284657](http://www.pivotaltracker.com/story/37284657)
53
- * SHA: ad8f6c839bce5d362409e59c46043b0ecc762faf
54
- * Gregg Van Hove and Tim Jarratt, pair+gvanhove+tjarratt@pivotallabs.com
55
-
56
-
57
- ### In RC3
58
-
59
- * Better re-work of Runners and Formatters
60
- * In Rails 4, turn off turbolink processing of jasmine runner spec links so spec links work
61
- * User can copy `boot.js` into their project for customization - usage: `jasmine copy_boot_js`
62
- * Allow user to configure path to `jasmine.yml` via an ENV variable.
63
- * More data printed out to console when starting the Jasmine server
64
- * Support for specs to be written in CoffeeScript when used with Rails
65
- * Fix stylesheet asset expansion for Rails 4
66
- * Remove RSpec dependency - Jasmine gem builds its own output
67
- * Remove Selenium dependency - builds run against PhantomJS by default
68
- * Remove accidental sqllite development dependency
69
- * Jasmine example code no longer installed when `jasmine init` is run. Examples are now installed explicitly with `jasmine examples`
70
- * Extraction to separate gems for:
71
- * JUnit XML formatter
72
- * Selenium/Webdriver integration
73
-
74
- ## Accepted Pull Requests
75
-
76
- * Fix README.markdown and add config example #[144](http://github.com/pivotal/jasmine-gem/pull/144) from @enrapt-mochizuki
77
- * Use a relative path to jasmine repo in Gemfile #[161](http://github.com/pivotal/jasmine-gem/pull/161) from @zephyr-dev
78
- * Problem when using a asset prefix other than '/assets' #[155](http://github.com/pivotal/jasmine-gem/pull/155) from @janv
79
- * Remove unused code - #[154](http://github.com/pivotal/jasmine-gem/pull/154) from @daytonn
80
- * Fix default path for :spec_helper in template #[147](http://github.com/pivotal/jasmine-gem/pull/147) from @kmayer
81
- * Improve Gemfile installation instructions #[141](http://github.com/pivotal/jasmine-gem/pull/141)
82
-
83
- ### In RC3
84
-
85
- * Use IE=edge for IE compatibility because this will put IE into the highest available mode for each version of IE - see [Question on StackOverflow](http://stackoverflow.com/questions/3449286/force-ie-compatibility-mode-off-in-ie-using-tags
86
- ) - #[168](http://github.com/pivotal/jasmine-gem/pull/168) from @iwz
87
-
88
-
89
- ------
90
-
91
- _Release Notes generated with [Anchorman](http://github.com/infews/anchorman)_
92
-
93
- [selenium]: https://github.com/jasmine/jasmine_selenium_runner
94
- [junit]: https://github.com/jasmine/jasmine_junitxml_formatter