execution.feature in polytrix-0.1.0

- old
+ new

@@ -2,19 +2,11 @@
 
   Polytrix uses the [script/bootstrap](http://wynnnetherland.com/linked/2013012801/bootstrapping-consistency) pattern to prepare SDKs for testing. You can hook into any package manager, compiler, build tool, or any other toolchain to prepare to build and run samples.
 
   Polytrix also sets up tags for the SDKs so you can use the normal rspec `-t` option to select which SDK to run.
 
-  Scenario: Bootstrap an SDK
-    Given the java SDK
-    And the empty polytrix config
-    And the standard rspec setup
-    When I run `bundle exec rspec`
-    Then the output should contain ":compileJava"
-    And the output should contain "BUILD SUCCESSFUL"
-
-Scenario: Running all SDKs
+  Scenario: Running all SDKs
     Given the ruby SDK
     And the java SDK
     And the python SDK
     And the hello_world polytrix config
     And the standard rspec setup
@@ -39,17 +31,10 @@
     And the standard rspec setup
     And a file named "spec/custom_spec.rb" with:
     """
     require 'polytrix/rspec'
 
-    Polytrix.configure do |polytrix|
-      Dir['sdks/*'].each do |sdk|
-        polytrix.implementor sdk
-      end
-      polytrix.test_manifest = 'polytrix_tests.yml'
-    end
-
     # This is more of an integration test, but makes sure the rspec API is working.
     # Expect results to all be pending, because there's no implementors in this proj.
 
     Polytrix.validate(suite: 'Katas', sample: 'hello world') do |challenge|
       # You can make assertions about the process using the Mixlib::ShellOut API
@@ -60,8 +45,9 @@
 
     Polytrix.validate(suite: 'Katas', sample: 'quine') do |challenge|
       expect(challenge[:result].execution_result.stdout).to eq File.read(challenge[:result].source)
     end
     Polytrix.load_tests
+
     """
     When I run `bundle exec rspec spec/custom_spec.rb`
     And the output should match /expected: 1\s+got: 0/