knapsack 1.12.0 → 1.12.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2b142dc2475ee898b18ffea634b8f5619853685f
-  data.tar.gz: fe681da00799d3027ebcc1fafb4a2c3d9f118f1a
+  metadata.gz: 653d9e7ac72466dc9713aeee4d5b42af3e0f065a
+  data.tar.gz: d67c45587bae5c80ea6ea74761918f8c4247a8d7
 SHA512:
-  metadata.gz: 6da196cf8d1436d5111ba796311d25d828c518b1d38ff8730c28bc9ce3901a5b3dedc1b1fb2180f7517fbb648503de97f001858baa627ef46577b641fb9edeb3
-  data.tar.gz: 40341a7b90caf3537994ec8f08748ba04dafa57b7f4fca6829c2dc7d498c9d84d975a42dc7d39cd462c09861c0a7240c651f3ab60073e8e0cd16095e56b1b0fe
+  metadata.gz: 343c3e23963c1d81159394870f4b18237ac31c55fe6cf01e27146479f71e019c99a49149934ec00c9d10b425180b8d370eb6bf2df9c6960bde5b5f0d2dbf2799
+  data.tar.gz: 711f1ea47f5c2b657727b3ae2d722f459ba35efe8729e73d9e8f57995c1c3c1f88a5ea2d56092d27066fa6b8f650b7101c2c6fb3d1ad077ccbecbcb3ee37684d

data/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 * TODO
 
+### 1.12.1
+
+* Cucumber and Spinach should load files from proper folder in case when you use custom test directory.
+
+https://github.com/ArturT/knapsack/compare/v1.12.0...v1.12.1
+
 ### 1.12.0
 
 * Add support for Minitest::SharedExamples

data/README.md

@@ -16,13 +16,6 @@
 
 Parallel tests across CI server nodes based on each test file's time execution. Knapsack generates a test time execution report and uses it for future test runs.
 
-Presentations about gem:
-
-* [X 2014 Kraków Ruby User Group](http://slides.com/arturt/parallel-tests-in-comparable-time)
-* [VII 2014 Lunar Logic Dev Meeting](http://slides.com/arturt/knapsack)
-
-**Would you like to try [knapsack_pro gem](https://github.com/KnapsackPro/knapsack_pro-ruby) with more features and free access for beta users? Please [visit Knapsack Pro](http://knapsackpro.com).**
-
 ### Without Knapsack
 
 ![Without Knapsack gem](docs/images/without_knapsack.png)
@@ -31,6 +24,21 @@ Presentations about gem:
 
 ![With Knapsack gem](docs/images/with_knapsack.png)
 
+### Features
+
+| Feature | knapsack gem | knapsack_pro gem
+| --- | :---: | :---:
+| Test suite split based on tests time execution | ✔ | ✔
+| Automated tests time execution recording | ✘ | ✔
+| Test suite split based on most up to date tests time execution data | ✘ | ✔
+| [Show all features](https://knapsackpro.com/features?utm_source=github&utm_medium=readme&utm_campaign=knapsack_gem&utm_content=show_all_features) | |
+
+**Would you like to try [knapsack_pro gem](https://github.com/KnapsackPro/knapsack_pro-ruby) with more features and free access for early users? Please [visit Knapsack Pro](http://knapsackpro.com?utm_source=github&utm_medium=readme&utm_campaign=knapsack_gem&utm_content=try_knapsack_pro).**
+
+### Presentations about knapsack gem
+
+* [X 2014 Kraków Ruby User Group](http://slides.com/arturt/parallel-tests-in-comparable-time)
+* [VII 2014 Lunar Logic Dev Meeting](http://slides.com/arturt/knapsack)
 
 <!-- START doctoc generated TOC please keep comment here to allow auto update -->
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
@@ -591,7 +599,7 @@ If you want to regenerate report take a look [here](#common-step).
 
 `KNAPSACK_GENERATE_REPORT=true bundle exec rspec spec`
 
-If you run command like this on your development machine then test suite time execution might be different than if you generate a report on CI machine (for instance tests might be faster on your machine then on CI node) so that might be a reason why you see warning about regenerating report. You can generate the report on single CI node which should give you result specific for your CI node instead of your development machine. In case you don't want to bother about manually regenerating knapsack report please take a look on [knapsack_pro gem](http://knapsackpro.com).
+If you run command like this on your development machine then test suite time execution might be different than if you generate a report on CI machine (for instance tests might be faster on your machine then on CI node) so that might be a reason why you see warning about regenerating report. You can generate the report on single CI node which should give you result specific for your CI node instead of your development machine. In case you don't want to bother about manually regenerating knapsack report please take a look on [knapsack_pro gem](http://knapsackpro.com?utm_source=github&utm_medium=readme&utm_campaign=knapsack_gem&utm_content=no_manual_report).
 
 ### What does "leftover specs" mean?
 

data/lib/knapsack/runners/cucumber_runner.rb

@@ -12,7 +12,7 @@ module Knapsack
         Knapsack.logger.info allocator.leftover_node_tests
         Knapsack.logger.info
 
-        cmd = %Q[bundle exec cucumber #{args} -- #{allocator.stringify_node_tests}]
+        cmd = %Q[bundle exec cucumber #{args} --require #{allocator.test_dir} -- #{allocator.stringify_node_tests}]
 
         system(cmd)
         exit($?.exitstatus) unless $?.exitstatus.zero?

data/lib/knapsack/runners/spinach_runner.rb

@@ -12,7 +12,7 @@ module Knapsack
         Knapsack.logger.info allocator.leftover_node_tests
         Knapsack.logger.info
 
-        cmd = %Q[bundle exec spinach #{args} -- #{allocator.stringify_node_tests}]
+        cmd = %Q[bundle exec spinach #{args} --features_path #{allocator.test_dir} -- #{allocator.stringify_node_tests}]
 
         system(cmd)
         exit($?.exitstatus) unless $?.exitstatus.zero?

data/lib/knapsack/version.rb

@@ -1,3 +1,3 @@
 module Knapsack
-  VERSION = '1.12.0'
+  VERSION = '1.12.1'
 end

data/test_examples/fast/shared_examples_test.rb

@@ -1,5 +1,4 @@
 require 'test_helper'
-require 'minitest/spec'
 
 class Minitest::SharedExamples < Module
   include Minitest::Spec::DSL

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: knapsack
 version: !ruby/object:Gem::Version
-  version: 1.12.0
+  version: 1.12.1
 platform: ruby
 authors:
 - ArturT
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-09-04 00:00:00.000000000 Z
+date: 2016-09-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake