teaspoon 1.0.0 → 1.0.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: c553b99135614e7bb23eed05345ed59212f039e3
4
- data.tar.gz: 6ba9d3c79c72c60db28085f782b43be8e3886cfa
3
+ metadata.gz: 17feb8da692ba7ff472c5bf6d3735085ab3ad6e4
4
+ data.tar.gz: 33e3ca26a7d1d24b20238eeebeb8b679d6751dd2
5
5
  SHA512:
6
- metadata.gz: 516511f761bb5a5b9348d7cd94d73c427dc8bbf59172ebbc8bcdf5129f1c43940e049982d8279b81f2afe88eb146e8895f054135c1dacc2e94d6235bd6a44b3b
7
- data.tar.gz: 1e9dc21951bcc43c34b2a144950f3cdde30b05be200583b792697520adb1307481e5d628f1b0d5a76bcb0c2680f2730102d19adaabd7f31e6c0c8116a9d4155f
6
+ metadata.gz: 912fef66a4bb0eb74c877c821c1b7e4ad0dd20a30897e6de8e5c95392085424b8a0e7f0a58c917fe01154353c8d9aac3d377f301b01186ec14184bf78883ae13
7
+ data.tar.gz: 1e09ccfd90a16392134f958350f3eb41b7bd70e042896852a5b0df9c8c3bdd79848fbce9f2c5b55ec34f465fc2f80ea1fbbda0d8ddd82f4d6ae7710f2fe51e79
data/CHANGELOG.md CHANGED
@@ -1,4 +1,14 @@
1
- ### 1.0.0 (unreleased)
1
+ ### Unreleased
2
+
3
+
4
+ ### 1.0.1 (5/5/15)
5
+
6
+ #### Bug Fixes
7
+
8
+ * Fix constant scoping for Phantomjs (#359)
9
+
10
+
11
+ ### 1.0.0 (5/4/15)
2
12
 
3
13
  #### Upgrade Steps
4
14
 
@@ -9,8 +19,8 @@
9
19
  If you had Teaspoon locked at a specific version, kill the version. You'll now need to reference the version of the framework, instead of the version of Teaspoon.<br>
10
20
  eg: If your Gemfile has `gem 'teaspoon', '0.9.1'` and you're using Mocha, you'll want your Gemfile to reference the latest version of Mocha: `gem 'teaspoon-mocha', '2.2.4'`. The teaspoon-mocha gem contains previous versions of Mocha, so even if you're not using version 2.2.4 of Mocha in your `teaspoon_env.rb`, still reference the latest version in your Gemfile and the older version should still work.
11
21
 
12
- - **Update your coverage configuration in teaspoon_env.rb**<br>
13
- If you use Teaspoon to generate coverage reports with Istanbul, and you use the `suite.no_coverage` to exclude files from coverage, you'll need to migrate that configuration into the `config.coverage` blocks. So if you have:
22
+ - **Configuration: Update your coverage**<br>
23
+ In `teaspoon_env.rb`, if you use Teaspoon to generate coverage reports with Istanbul, and you use the `suite.no_coverage` to exclude files from coverage, you'll need to migrate that configuration into the `config.coverage` blocks. So if you have:
14
24
 
15
25
  ```ruby
16
26
  suite.no_coverage += /my_file.js/
@@ -27,23 +37,21 @@
27
37
  This means that you can no longer exclude things at the suite level. If you had multiple suites with different `no_coverage` configurations, you'll now need to create multiple coverage blocks and specify the coverage you want when using the CLI.
28
38
  eg: teaspoon --coverage=[coverage_name]
29
39
 
30
- - **Ensure suite.javascripts and suite.stylesheets are appending asset**<br>
31
- If you use `suite.javascripts` or `suite.stylesheets`, make sure you're appending assets into the array instead of assigning the array.
40
+ - **Configuration: Prefer suite.use_framework over suite.javascripts**<br>
41
+ Teaspoon now has better support for framework versions. In `teaspoon_env.rb`, if you are using `suite.javascripts` to include the testing framework, you should use `suite.use_framework` with a version number instead.
32
42
 
33
- eg: In Teaspoon 0.9.1, you might have:
43
+ If your `teaspoon_env.rb` has `suite.javascripts` configured:
34
44
 
35
45
  ```ruby
36
- suite.javascripts = ["jasmine/1.3.1", "teaspoon-jasmine", "custom-js-file"]
46
+ suite.javascripts = ["jasmine/1.3.1", "teaspoon-jasmine", "your-custom-file.js"]
37
47
  ```
38
48
 
39
- This will fail as "jasmine/1.3.1" and "teaspoon-jasmine" no longer exist. Teaspoon will automatically add the framework assets to the array for you, so you should append assets instead:
49
+ This will break since `teaspoon-jasmine` no longer exists. Update this config to exclude any framework or Teaspoon files. Be sure to use `+=` as Teaspoon will be modifying this array to append framework and Teaspoon files.
40
50
 
41
51
  ```ruby
42
- suite.javascripts += ["custom-js-file"]
52
+ suite.javascripts += ["your-custom-file.js"]
43
53
  ```
44
54
 
45
- Likewise for `suite.stylesheets`.
46
-
47
55
  #### Enhancements
48
56
 
49
57
  * Break frameworks out into individual gems (eg teaspoon-mocha)
@@ -51,7 +51,7 @@ module Teaspoon
51
51
  def executable
52
52
  return @executable if @executable
53
53
  @executable = which("phantomjs")
54
- @executable = Phantomjs.path if @executable.blank? && defined?(::Phantomjs)
54
+ @executable = ::Phantomjs.path if @executable.blank? && defined?(::Phantomjs)
55
55
  return @executable unless @executable.blank?
56
56
  raise Teaspoon::MissingDependencyError.new("Unable to locate phantomjs. Install it or use the phantomjs gem.")
57
57
  end
@@ -1,3 +1,3 @@
1
1
  module Teaspoon
2
- VERSION = "1.0.0"
2
+ VERSION = "1.0.1"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: teaspoon
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.0
4
+ version: 1.0.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - jejacks0n
@@ -11,7 +11,7 @@ authors:
11
11
  autorequire:
12
12
  bindir: bin
13
13
  cert_chain: []
14
- date: 2015-05-04 00:00:00.000000000 Z
14
+ date: 2015-05-05 00:00:00.000000000 Z
15
15
  dependencies:
16
16
  - !ruby/object:Gem::Dependency
17
17
  name: railties