effective_test_bot 0.7.0 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 093fb572d5025d9dca6e4b329bbf91bc49e750c2
-  data.tar.gz: 988f87d788c34488bbd053dcd37170f1b71e5df2
+  metadata.gz: 64b44fba9d50f01fd32b612de3d11d810c6ba12a
+  data.tar.gz: a07e93aee37f18a0af63098c6ac6ac540d61d8a8
 SHA512:
-  metadata.gz: 3343f40a9560c374e5e5a647c1d92ef6d4e66883f093f516573d6262c55c6c18ca4924bcf11c0183c97192490399c984700b42689feb9e9e59bb77b105174813
-  data.tar.gz: d43e839d353d45600703450a2030dac2c2751616e48902ec8078291a3f6836f676e6047f0459783d3683336e6d3c44646e1942f645cd79429e8375db884e5c6a
+  metadata.gz: 5ba5cc490a7296da4d6a82f33faa5cc7bce2f8b2cbe29b01b913812bd59963b0381d73c58d886792144a8a318f27c56389ebdbc5412451abcf624863f0e6bbc7
+  data.tar.gz: fc19738de32fde123f04dd8b606eb17627236601323dc8a9267d58a5d88ca195a467943a97a5ba9efb9fe6a0004b8711bb1fc3c37ffe1863f69309e391a1c75f

data/README.md

@@ -2,32 +2,32 @@
 
 Stop testing and start test botting.
 
-A [minitest](https://github.com/seattlerb/minitest) library of [capybara](https://github.com/jnicklas/capybara) based feature tests that should pass in every Ruby on Rails application.
+A [minitest](https://github.com/seattlerb/minitest) library of [capybara](https://github.com/jnicklas/capybara) based Rails System Tests that should pass in every Ruby on Rails application.
 
 Adds many additional assertions and quality of life helper functions.
 
 Provides a curated set of minitest and capybara focused rails testing gems and a well configured `test_helper.rb` file.
 
-Run `rails test:bot:environment` to validate your testing environment.  Ensures that all fixtures and seeds are properly initialized.  Makes sure database transactions and web sessions correctly reset between tests.
+Run `rails test:bot:environment` to validate your testing environment. Ensures that all fixtures and seeds are properly initialized. Makes sure database transactions and web sessions correctly reset between tests.
 
 Adds many class and instance level 1-liners to run entire test suites and check many assertions all at once.
 
 Autosaves an animated .gif for any failing test.
 
-Run `rails test:bot` to automatically check every route in your application against an appropriate test suite, without writing any code.  Clicks through every page, intelligently fills forms with appropriate pseudo-random input and checks for all kinds of errors and omissions.
+Run `rails test:bot` to automatically check every route in your application against an appropriate test suite, without writing any code. Clicks through every page, intelligently fills forms with appropriate pseudo-random input and checks for all kinds of errors and omissions.
 
 Turn on tour mode to programatically generate an animated .gif of every workflow in your website.
 
 Make sure everything actually works.
 
-## Capybara Webkit
 
-This is the `capybara` branch of effective_test_bot which supports Rails <= 5.1 and Capybara Webkit.
+## Rails System Tests
 
-All published effective_test_bot 0.x gems will support Rails <= 5.1 and Capybara Webkit.
+This is the 'Rails System Test' branch of effective_test_bot.
 
-For Rails 5.2+ please see the master branch and/or effective_test_bot 1.x gems.
+This requires Rails 5.1+
 
+Please check out [Effective TestBot Capybara-Webkit branch](https://github.com/code-and-effect/effective_test_bot/tree/capybara-webit) for more information using this gem with Capybara Webkit and Rails < 5.1.
 
 ## Getting Started
 
@@ -120,10 +120,8 @@ The following assertions are added for use in any integration test:
 - `assert_email(action)` asserts an email with the given action name was sent. Also supports `assert_email(to: email)` type syntax with to, from, subject, body.
 - `assert_flash`, optionally with the desired `:success`, `:error` key and/or message, makes sure the flash is set.
 - `assert_jquery_ujs_disable_with` makes sure all `input[type=submit]` elements on the page have the `data-disable-with` property set.
-- `assert_no_exceptions` checks for any exceptions in the last page request and gives a stacktrace if there was.
 - `assert_no_html_form_validation_errors` checks for frontend html5 errors.
-- `assert_no_js_errors` - checks for any javascript errors on the page.
-- `assert_no_unpermitted_params` makes sure the last submitted form did not include any unpermitted params and prints out any unpermitted params that do exist.
+- `assert_no_js_errors` checks for any javascript errors on the page.
 - `assert_page_content(content)` checks that the given content is present without waiting the capybara default wait time.
 - `assert_no_page_content(content)` checks that the given content is blank without waiting the capybara default wait time.
 - `assert_page_status` checks for a given http status, default 200.
@@ -135,7 +133,7 @@ The following assertions are added for use in any integration test:
 
 As well,
 
-- `assert_page_normal` checks for general errors on the current page.  Checks include  `assert_no_exceptions`, `assert_page_status`, `assert_no_js_errors`, and `assert_page_title`.
+- `assert_page_normal` checks for general errors on the current page. Checks include `assert_page_status`, `assert_no_js_errors`, and `assert_page_title`.
 
 ## Capybara Extras
 
@@ -156,10 +154,13 @@ It clicks through bootstrap tabs and fill them nicely left-to-right, one tab at
 You can pass a Hash of 'fills' to specify specific input values:
 
 ```ruby
-class PostTest < Capybara::Rails::TestCase
+# app/test/system/posts_test.rb
+require 'application_system_test_case'
+
+class PostTest < ApplicationSystemTestCase
   test 'creating a new post' do
     visit new_post_path
-    fill_form(:title => 'A Cool Post', 'author.last_name' => 'Smith')
+    fill_form(title: 'A Cool Post', 'author.last_name': 'Smith')
     submit_form
   end
 end
@@ -168,10 +169,10 @@ end
 And you can disable specific fields from being filled, by modifying the input html in your normal view:
 
 ```ruby
-= f.input :too_complicated, 'data-test-bot-skip' => true
+= f.input :too_complicated, 'data-test-bot-skip': true
 ```
 
-Sometimes you have the requirement that inputs add upto a certain number.  For example, having to provide percentages in 3-4 input fields that always add upto 100%.
+Sometimes you have the requirement that inputs add upto a certain number. For example, having to provide percentages in 3-4 input fields that always add upto 100%.
 
 You can use the html `min` and `max` properties to indicate this requirement.
 
@@ -188,7 +189,9 @@ Clicks the first `input[type='submit']` field (or first submit field with the gi
 Automatically checks for `assert_no_html5_form_validation_errors`, `assert_jquery_ujs_disable_with` and `assert_no_unpermitted_params`
 
 ```ruby
-class PostTest < Capybara::Rails::TestCase
+require 'application_system_test_case'
+
+class PostTest < ApplicationSystemTestCase
   test 'creating a new post' do
     visit(new_post_path) and fill_form
     submit_form    # or submit_form('Save and Continue')
@@ -207,22 +210,20 @@ end
 - `sign_up` visits the devise `new_user_registration_path` and signs up as a new user.
 - `synchronize!` should fix any timing issues waiting for page elements.
 - `was_redirect?` returns true/false if the last time we changed pages was a 304 redirect.
-- `was_download?` if clicking a link returned a file of any type rather than a page change.
 - `within_if(selector, boolean) do .. end` runs the block inside capybara's `within do .. end` if boolean is true, otherwise runs the same block skipping the `within`.
 
 ## Capybara Super Extras
 
-Running integration tests with [capybara-webkit](https://github.com/thoughtbot/capybara-webkit) is truly a black-box integration testing experience.  This provides a lot of benefits, but also some severe limitations.
+Running system tests is supposed to be a black-box integration testing experience. This provides a lot of benefits, but also some severe limitations.
 
-The test web server runs in a totally separate process.  It knows nothing about your application and it does not have access to any of the rails internal state. It only sees html, javascript, css and urls.
+The test web server runs in a totally separate process. It knows nothing about your application and it does not have access to any of the rails internal state. It only sees html, javascript, css and urls.
 
-effective_test_bot fills in this knowledge gap by serializing any interesting values within the http header.  This gives our tests a way to peek inside the black box.
+effective_test_bot fills in this knowledge gap by serializing any interesting values with a javascript payload. This gives our tests a way to peek inside the black box.
 
 The following representations of the rails internal state are made available:
 
-- `assigns` a Hash representation of the current page's rails `view_assigns`. Serializes any `ActiveRecord` objects, as well as any `TrueClass`, `FalseClass`, `NilClass`, `String`, `Symbol`, and `Numeric` objects.  Does not serialize anything else, but sets a symbol `assigns[key] == :present_but_not_serialized`.
+- `assigns` a Hash representation of the current page's rails `view_assigns`. Serializes any `ActiveRecord` objects, as well as any `TrueClass`, `FalseClass`, `NilClass`, `String`, `Symbol`, and `Numeric` objects. Does not serialize anything else, but sets a symbol `assigns[key] == :present_but_not_serialized`.
 - `flash` a Hash representation of the current page's flash.
-- `unpermitted_params` an Array of any unpermitted parameters that were encountered by the last request.
 
 ## Effective Test Suites
 
@@ -248,19 +249,20 @@ The following instance level `crud_action_test` methods are available:
 - `crud_action_test(:edit)` signs in as the given user, finds or creates a resource, visits `edit_resource_path` and checks that an appropriate form exists for this resource.
 - `crud_action_test(:update_invalid)` signs in as the given user, finds or creates a resource, visits `edit_resource_path` and submits an empty form.  Checks that the existing resource wasn't updated and that all errors are properly assigned and displayed.
 - `crud_action_test(:update_valid)` signs in as the given user, finds or creates a resource, visits `edit_resource_path` and submits a valid form. Checks for any errors and makes sure the existing resource was updated.
-- `crud_action_test(:destroy)` signs in as the given user, finds or creates a resource, visits `resources_path`.  It then finds or creates a link to destroy the resource and clicks the link.  Checks for any errors and makes sure the resource was deleted.  If the resource `respond_to?(:archived)` it will check for archive behavior instead of delete.
+- `crud_action_test(:destroy)` signs in as the given user, finds or creates a resource, visits `resources_path`.  It then finds or creates a link to destroy the resource and clicks the link. Checks for any errors and makes sure the resource was deleted. If the resource `respond_to?(:archived)` it will check for archive behavior instead of delete.
 
 Also,
 
-- `crud_action_test(:tour)` signs in as a given user and calls all the above `crud_action_test` methods from inside one test.  The animated .gif produced from this test suite records the entire process of creating, showing, editing and deleting a resource from start to finish.  It makes all the same assertions as running the test suites individually.
+- `crud_action_test(:tour)` signs in as a given user and calls all the above `crud_action_test` methods from inside one test. The animated .gif produced from this test suite records the entire process of creating, showing, editing and deleting a resource from start to finish. It makes all the same assertions as running the test suites individually.
 
-
-A quick note on speed:  You can speed up these test suites by fixturing, seeding or first creating an instance of the resource being tested. Any tests that need to `find_or_create_resource` check for an existing resource first, otherwise visit `new_resource_path` and submit a form to create the resource.  Having a resource already created will speed things up.
+A quick note on speed: You can speed up these test suites by fixturing, seeding or first creating an instance of the resource being tested. Any tests that need to `find_or_create_resource` check for an existing resource first, otherwise visit `new_resource_path` and submit a form to create the resource. Having a resource already created will speed things up.
 
 There are a few variations on the one-liner method:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+require 'application_system_test_case'
+
+class PostTest < ApplicationSystemTestCase
   # Runs all 9 crud_action tests against /posts
   crud_test(resource: Post)
 
@@ -284,7 +286,9 @@ end
 The individual test suites may also be used as part of a larger test:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+require 'application_system_test_case'
+
+class PostTest < ApplicationSystemTestCase
   test 'user may only update a post once' do
     crud_action_test(test: :create_valid, resource: Post, user: User.first)
     assert_text 'successfully created post.  You may only update it once.'
@@ -312,7 +316,7 @@ This test runs through the the [devise](https://github.com/plataformatec/devise)
 Use as a one-liner:
 
 ```ruby
-class MyApplicationTest < Capybara::Rails::TestCase
+class MyApplicationTest < ApplicationSystemTestCase
   devise_test  # Runs all tests (sign_up, sign_in_valid, and sign_in_invalid)
 end
 ```
@@ -320,7 +324,7 @@ end
 Or each individually in part of a regular test:
 
 ```ruby
-class MyApplicationTest < Capybara::Rails::TestCase
+class MyApplicationTest < ApplicationSystemTestCase
   test 'user receives 10 tokens after signing up' do
     devise_action_test(test: :sign_up)
     assert_text 'Tokens: 10'
@@ -345,7 +349,7 @@ This test signs in as the given user, visits the given controller/action/page an
 Use it as a one-liner:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+class PostsTest < ApplicationSystemTestCase
   # Uses find_or_create_resource! to load a seeded resource or create a new one
   member_test(controller: 'posts', action: 'unarchive', user: User.first)
 
@@ -357,7 +361,7 @@ end
 Or as part of a regular test:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+class PostsTest < ApplicationSystemTestCase
   test 'posts can be unarchived' do
     post = Post.create(title: 'first post', archived: true)
 
@@ -375,7 +379,7 @@ This test signs in as the given user, visits the given page and simply checks `a
 Use it as a one-liner:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+class PostsTest < ApplicationSystemTestCase
   page_test(path: :posts_path, user: User.first)  # Runs the page_test test suite against posts_path as User.first
 end
 ```
@@ -383,7 +387,7 @@ end
 Or as part of a regular test:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+class PostsTest < ApplicationSystemTestCase
   test 'posts are displayed on the index page' do
     Post.create(title: 'first post')
 
@@ -402,7 +406,7 @@ This test signs in as the given user, visits the given page then checks `assert_
 Use it as a one-liner:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+class PostsTest < ApplicationSystemTestCase
   # Visits /blog and tests that it redirects to a working /posts page
   redirect_test(from: '/blog', to: '/posts', user: User.first)
 end
@@ -411,7 +415,7 @@ end
 Or as part of a regular test:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+class PostsTest < ApplicationSystemTestCase
   test 'visiting blog redirects to posts' do
     Post.create(title: 'first post')
     redirect_action_test(from: '/blog', to: '/posts', user: User.first)
@@ -431,7 +435,7 @@ As well, in the `wizard_action_test`, each page is yielded to the calling method
 Use it as a one-liner:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+class PostsTest < ApplicationSystemTestCase
   wizard_test(from: '/build_post/step1', to: '/build_post/step5', user: User.first)
 end
 ```
@@ -439,7 +443,7 @@ end
 Or as part of a regular test:
 
 ```ruby
-class PostsTest < Capybara::Rails::TestCase
+class PostsTest < ApplicationSystemTestCase
   test 'building a post in 5 steps' do
     wizard_action_test(from: '/build_post/step1', to: '/build_post/step5', user: User.first) do
       if page.current_path.end_with?('step4')
@@ -491,9 +495,9 @@ Please see the installed `effective_test_bot.rb` initializer file for a full des
 
 Unfortunately, with the current day ruby on rails ecosystem, simply getting a testing environment setup correctly is a non-trivial endeavor filled with gotchas and many things that can go wrong.
 
-User sessions need to properly reset and database transactions must be correctly rolled back between tests.  Seeds and fixtures that were once valid may become invalid as the application changes.  Database migrations must stay up to date.  Capybara needs to query your app with a single shared connection or weird things start happening.
+User sessions need to properly reset and database transactions must be correctly rolled back between tests. Seeds and fixtures that were once valid may become invalid as the application changes. Database migrations must stay up to date. Capybara needs to query your app with a single shared connection or weird things start happening.
 
-Included with this gem is the `rails generate effective_test_bot:install` that does its best to provide a known-good set of configuration files that initialize all required testing gems.  However, every developer's machine is different, and there are just too many points of failure.  Everyone's `test/test_helper.rb` will be slightly different.
+Included with this gem is the `rails generate effective_test_bot:install` that does its best to provide a known-good set of configuration files that initialize all required testing gems. However, every developer's machine is different, and there are just too many points of failure. Everyone's `test/test_helper.rb` will be slightly different.
 
 Run `rails test:bot:environment` to check that capybara is doing the right thing, everything is reset properly between test runs, an initial user record exists, all seeded and fixtured data is valid, devise works and rails' jquery-ujs is present.
 
@@ -501,7 +505,7 @@ If all environment tests pass, you will have a great experience with automated t
 
 ## Automated full stack testing
 
-One of the main goals of `effective_test_bot` is to increase the speed at which tests can be written in any ruby on rails application.  Well, there's no faster way of writing tests than by not writing them at all.
+One of the main goals of `effective_test_bot` is to increase the speed at which tests can be written in any ruby on rails application. Well, there's no faster way of writing tests than by not writing them at all.
 
 Run `rails test:bot` to scan every route defined in `routes.rb` and run an appropriate test suite.
 
@@ -522,17 +526,12 @@ rails test:bot TEST=posts#index
 
 ## Animated gifs and screenshots
 
-Call `save_test_bot_screenshot` from within any test to take a screenshot of the current page.  If an animated .gif is produced at the end of the test -- either from autosave_animated_gif_on_failure or tour mode -- this screenshot will be used as one of the frames in the animation.
+Call `save_test_bot_screenshot` from within any test to take a screenshot of the current page. If an animated .gif is produced at the end of the test -- either from autosave_animated_gif_on_failure or tour mode -- this screenshot will be used as one of the frames in the animation.
 
 This method is already called by `fill_form` and `submit_form`.
 
 To disable taking screenshots entirely set `config.screenshots = false` in the `config/initializers/effective_test_bot.rb` initializer file.
 
-### Autosave on failure
-
-The `test/test_helper.rb` file that is installed by `effective_test_bot` enables [capybara-screenshot](https://github.com/mattheworiordan/capybara-screenshot)'s `autosave_on_failure` functionality.  So whenever a test fails, the current html will be written and a .png screenshot will be saved.  This is invaluable for troubleshooting why a test has failed.
-
-Building on this type of feature, `effective_test_bot` will also autosave an animated gif on failure.  This does slow down failing tests and can be disabled.
 
 ### Tour mode
 

data/app/helpers/effective_test_bot_controller_helper.rb

@@ -1,44 +1,36 @@
 module EffectiveTestBotControllerHelper
-  # This is included as an after_filter
-  def assign_test_bot_http_headers
-    response.headers['Test-Bot-Flash'] = Base64.encode64(flash.to_hash.to_json)
+  BODY_TAG = '</body>'
 
-    # Assign the Assigns now
-    # With the assigns, we're a little bit more selective
-    # Anything that's a simple object can be serialized
-    test_bot_assigns = {}
+  # This is included as an after_action in the controller
+  def assign_test_bot_payload(payload = {})
+    return unless response.content_type == 'text/html'.freeze
+    return unless !!(response.body[BODY_TAG])
 
-    view_assigns.each do |key, object|
-      case object
-      when ActiveRecord::Base
-        test_bot_assigns[key] = object.attributes
-        test_bot_assigns[key][:errors] = object.errors.messages.delete_if { |_, v| v.blank? } if object.errors.present?
-      when (ActiveModel::Model rescue nil)
-        test_bot_assigns[key] = object.respond_to?(:attributes) ? object.attributes : {present_but_not_serialized: true}
-        test_bot_assigns[key][:errors] = object.errors.messages.delete_if { |_, v| v.blank? } if object.errors.present?
-      when TrueClass, FalseClass, NilClass, String, Symbol, Numeric
-        test_bot_assigns[key] = object
-      else
-        # We don't want to serialize them, but they should be present
-        test_bot_assigns[key] = :present_but_not_serialized
-      end
+    payload.merge!({ response_code: response.code, assigns: test_bot_view_assigns, flash: flash.to_hash })
+
+    payload = view_context.content_tag(:script, id: 'test_bot_payload') do
+      [
+        '',
+        'window.effective_test_bot = {};',
+        payload.map { |k, v| "window.effective_test_bot.#{k} = #{v.respond_to?(:to_json) ? v.to_json : ("'" + v + "'")};" },
+        '',
+      ].join("\n").html_safe
     end
 
-    response.headers['Test-Bot-Assigns'] = Base64.encode64(test_bot_assigns.to_hash.to_json)
+    split = response.body.split(BODY_TAG)
+    response.body = "#{split.first}#{payload}#{BODY_TAG}#{split.last if split.size > 1}"
   end
 
-  # We get here if ApplicationController raised a ActionController::UnpermittedParameters error
-  def assign_test_bot_unpermitted_params_header(exception)
-    if exception.kind_of?(ActionController::UnpermittedParameters)
-      response.headers['Test-Bot-Unpermitted-Params'] = Base64.encode64(exception.params.to_json)
-    end
+  # This is called in an ActionController rescue_from.
+  def assign_test_bot_access_denied_exception(exception)
+    assign_test_bot_payload(test_bot_access_denied(exception))
   end
 
-  def assign_test_bot_access_denied_exception(exception)
-    return unless Rails.env.test?
+  private
 
-    response.headers['Test-Bot-Access-Denied'] = Base64.encode64({
-      exception: exception,
+  def test_bot_access_denied(exception)
+    {
+      access_denied: exception,
       action: exception.action,
       subject: (
         if exception.subject.kind_of?(Symbol)
@@ -49,7 +41,29 @@ module EffectiveTestBotControllerHelper
           exception.subject.class.name
         end
       )
-    }.to_json)
+    }
+  end
+
+  def test_bot_view_assigns
+    assigns = {}
+
+    view_assigns.each do |key, object|
+      case object
+      when ActiveRecord::Base
+        assigns[key] = object.attributes
+        assigns[key][:errors] = object.errors.messages.delete_if { |_, v| v.blank? } if object.errors.present?
+      when (ActiveModel::Model rescue nil)
+        assigns[key] = object.respond_to?(:attributes) ? object.attributes : { present_but_not_serialized: true }
+        assigns[key][:errors] = object.errors.messages.delete_if { |_, v| v.blank? } if object.errors.present?
+      when TrueClass, FalseClass, NilClass, String, Symbol, Numeric
+        assigns[key] = object
+      else
+        # We don't want to serialize them, but they should be present
+        assigns[key] = :present_but_not_serialized
+      end
+    end
+
+    assigns
   end
 
 end

data/config/application_system_test_case.rb

@@ -0,0 +1,8 @@
+require 'test_helper'
+
+class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
+  driven_by :selenium_chrome_headless, screen_size: [1024, 768]
+
+  include Warden::Test::Helpers if defined?(Devise)
+  include EffectiveTestBot::DSL
+end

data/config/test_helper.rb

@@ -1,59 +1,26 @@
-ENV['RAILS_ENV'] = 'test'
-require File.expand_path('../../config/environment', __FILE__)
+ENV['RAILS_ENV'] ||= 'test'
+require_relative '../config/environment'
+
 require 'rake'
 require 'rails/test_help'
-require 'minitest/rails'
-require 'minitest/rails/capybara'
-require 'minitest/pride'
-require 'minitest/reporters'
 
-require 'capybara/webkit'
-require 'capybara-screenshot/minitest'
-require 'capybara/slow_finder_errors'
-
-# require 'database_cleaner'
+require 'minitest/spec'
+require 'minitest/reporters'
+require 'minitest/fail_fast' if EffectiveTestBot.fail_fast?
 
 class ActiveSupport::TestCase
   # Setup all fixtures in test/fixtures/*.yml for all tests in alphabetical order.
   fixtures :all
-  use_transactional_fixtures = true
-end
-
-class Capybara::Rails::TestCase
-  # Make the Capybara DSL available in all integration tests
-  include Capybara::DSL
-  include Capybara::Assertions
-  include Capybara::Screenshot::MiniTestPlugin
-  include Warden::Test::Helpers if defined?(Devise)
-
-  include EffectiveTestBot::DSL
-
-  # Needed for Rails < 5.1
-  # def after_setup
-  #   super()
-  #   DatabaseCleaner.start
-  # end
 
-  # def after_teardown
-  #   super()
-  #   DatabaseCleaner.clean
-  #   Capybara.reset_sessions!  # Some apps seem to need this to correctly reset the test_06:_capybara_can_sign_in
-  # end
+  # For the let syntax
+  extend Minitest::Spec::DSL
 end
 
-Capybara.default_driver = :webkit
-Capybara.javascript_driver = :webkit
-Capybara::Screenshot.autosave_on_failure = true
-Capybara::Screenshot.prune_strategy = :keep_last_run
-Capybara::Screenshot.webkit_options = { width: 1024, height: 768 }
-Capybara::Webkit.configure { |config| config.allow_unknown_urls }
-
 Minitest::Reporters.use! Minitest::Reporters::SpecReporter.new
 
-# These three lines are needed as of minitest-reporters 1.1.2
 Rails.backtrace_cleaner.remove_silencers!
 Rails.backtrace_cleaner.add_silencer { |line| line =~ /minitest/ }
-Rails.backtrace_cleaner.add_silencer { |line| line =~ /effective_test_bot/ }
+#Rails.backtrace_cleaner.add_silencer { |line| line =~ /effective_test_bot/ }
 
 ###############################################
 ### Effective Test Bot specific stuff below ###
@@ -63,7 +30,7 @@ Rails.application.load_tasks
 
 # So the very first thing we do is consistently reset the database.
 # This can be done with Snippet 1 or Snippet 2.
-# Snippet 1 is faster, and will usually work.  Snippet 2 should always work.
+# Snippet 1 is faster, and will usually work. Snippet 2 should always work.
 
 # Snippet 1:
 Rake::Task['db:schema:load'].invoke
@@ -76,31 +43,6 @@ ActiveRecord::Migration.maintain_test_schema!
 # Rake::Task['db:migrate'].invoke
 
 # Now we populate our test data:
-Rake::Task['db:fixtures:load'].invoke # There's just no way to get the seeds first, as this has to delete everything
+Rake::Task['db:fixtures:load'].invoke
 Rake::Task['db:seed'].invoke
-Rake::Task['test:load_fixture_seeds'].invoke # This is included by effective_test_bot.  It just runs the app's test/fixtures/seeds.rb if it exists
-
-if EffectiveTestBot.fail_fast?
-  require 'minitest/fail_fast'
-end
-
-# "Connection not rolling back" snippets
-# These are some snippets that the internet has collected to fix test threading issues.
-# They are unneeded with effective_test_bot. On my machine. But I leave them here as a reference.
-# Try one or both if you are having issues passing rake test:bot:environment
-
-# class ActiveRecord::Base
-#   mattr_accessor :shared_connection
-#   @@shared_connection = nil
-
-#   def self.connection
-#     @@shared_connection || retrieve_connection
-#   end
-# end
-# ActiveRecord::Base.shared_connection = ActiveRecord::Base.connection
-
-# ActiveRecord::ConnectionAdapters::ConnectionPool.class_eval do
-#   def current_connection_id
-#     Thread.main.object_id
-#   end
-# end
+Rake::Task['test:load_fixture_seeds'].invoke # from effective_test_bot. Loads test/fixtures/seeds.rb

data/lib/effective_test_bot.rb

@@ -1,7 +1,6 @@
 require 'effective_resources'
 require 'effective_test_bot/engine'
 require 'effective_test_bot/dsl'
-require 'effective_test_bot/middleware'
 require 'effective_test_bot/version'
 
 module EffectiveTestBot

data/lib/effective_test_bot/engine.rb

@@ -7,27 +7,16 @@ module EffectiveTestBot
     config.autoload_paths += Dir["#{config.root}/test/support/**/"]
 
     # Set up our default configuration options.
-    initializer "effective_test_bot.defaults", :before => :load_config_initializers do |app|
+    initializer 'effective_test_bot.defaults', before: :load_config_initializers do |app|
       # Set up our defaults, as per our initializer template
       eval File.read("#{config.root}/config/effective_test_bot.rb")
     end
 
-    initializer 'effective_test_bot.middleware' do |app|
-      if Rails.env.test?
-        Rails.application.config.middleware.use EffectiveTestBot::Middleware
-      end
-    end
-
     initializer 'effective_test_bot.email_logger' do |app|
       if Rails.env.test?
         ActiveSupport.on_load :action_mailer do
           ActionMailer::Base.send :include, ::EffectiveTestBotMailerHelper
-
-          if ActionMailer::Base.respond_to?(:after_action)
-            ActionMailer::Base.send :after_action, :assign_test_bot_mailer_info
-          else
-            ActionMailer::Base.send :after_filter, :assign_test_bot_mailer_info
-          end
+          ActionMailer::Base.send :after_action, :assign_test_bot_mailer_info
         end
       end
     end
@@ -37,19 +26,8 @@ module EffectiveTestBot
         ActiveSupport.on_load :action_controller do
           ActionController::Base.send :include, ::EffectiveTestBotControllerHelper
 
-          if ActionController::Base.respond_to?(:before_action)
-            ActionController::Base.send :before_action, :expires_now # Prevent 304 Not Modified caching
-            ActionController::Base.send :after_action, :assign_test_bot_http_headers
-          else
-            ActionController::Base.send :before_filter, :expires_now # Prevent 304 Not Modified caching
-            ActionController::Base.send :after_filter, :assign_test_bot_http_headers
-          end
-
-          ApplicationController.instance_exec do
-            rescue_from ActionController::UnpermittedParameters do |exception|
-              assign_test_bot_unpermitted_params_header(exception)
-            end
-          end
+          ActionController::Base.send :before_action, :expires_now # Prevent 304 Not Modified caching
+          ActionController::Base.send :after_action, :assign_test_bot_payload
         end
       end
     end

data/lib/effective_test_bot/version.rb

@@ -1,3 +1,3 @@
 module EffectiveTestBot
-  VERSION = '0.7.0'.freeze
+  VERSION = '1.0.0'.freeze
 end

data/lib/generators/effective_test_bot/install_generator.rb

@@ -3,22 +3,17 @@ module EffectiveTestBot
     class InstallGenerator < Rails::Generators::Base
       include Rails::Generators::Migration
 
-      desc "Creates an EffectiveTestBot initializer in your application."
+      desc 'Creates an EffectiveTestBot initializer in your application.'
 
       source_root File.expand_path('../../templates', __FILE__)
 
-      def install_minitest
-        return if File.exist?('test/test_helper.rb')
-        puts '[effective_test_bot] installing minitest'
-        run 'bundle exec rails generate minitest:install'
-      end
-
       def copy_initializer
         template ('../' * 3) +  'config/effective_test_bot.rb', 'config/initializers/effective_test_bot.rb'
       end
 
-      def overwrite_minitest
+      def copy_test_helper
         template ('../' * 3) +  'config/test_helper.rb', 'test/test_helper.rb'
+        template ('../' * 3) +  'config/application_system_test_case.rb', 'test/application_system_test_case.rb'
       end
 
       def thank_you

data/lib/tasks/effective_test_bot_tasks.rake

@@ -1,5 +1,3 @@
-require 'rake/testtask'
-
 # rake test:bot
 # rake test:bot TEST=documents#new
 # rake test:bot TEST=documents#new,documents#show
@@ -27,11 +25,7 @@ namespace :test do
       ENV['TEST'] = nil
     end
 
-    if Gem::Version.new(Rails.version) < Gem::Version.new('5.0')
-      Rake::Task['test:effective_test_bot'].invoke
-    else
-      system("rails test #{File.dirname(__FILE__)}/../../test/test_bot/integration/application_test.rb")
-    end
+    system("rails test #{File.dirname(__FILE__)}/../../test/test_bot/system/application_test.rb")
   end
 
   desc "Runs 'rake test' with effective_test_bot tour mode enabled"
@@ -49,11 +43,7 @@ namespace :test do
   namespace :bot do
     desc 'Runs effective_test_bot environment test'
     task :environment do
-      if Gem::Version.new(Rails.version) < Gem::Version.new('5.0')
-        Rake::Task['test:effective_test_bot_environment'].invoke
-      else
-        system("rails test #{File.dirname(__FILE__)}/../../test/test_bot/integration/environment_test.rb")
-      end
+      system("rails test #{File.dirname(__FILE__)}/../../test/test_bot/system/environment_test.rb")
     end
 
     desc 'Deletes all effective_test_bot temporary, failure and tour screenshots'
@@ -114,26 +104,10 @@ namespace :test do
   end # /namespace bot
 
   desc 'loads test/fixtures/seeds.rb'
-  task :load_fixture_seeds => :environment do
+  task load_fixture_seeds: :environment do
     puts 'loading fixture seed'
     seeds = "#{Rails.root}/test/fixtures/seeds.rb"
     load(seeds) if File.exist?(seeds)
   end
 
-  # This ensures rake test:prepare is run before rake test:bot or rake test:bot:environment run
-  # Test files stuff is minitest hackery to just load the 1 test file
-  if Gem::Version.new(Rails.version) < Gem::Version.new('5.0')
-    Rake::TestTask.new('effective_test_bot' => 'test:prepare') do |t|
-      t.libs << 'test'
-      t.test_files = FileList["#{File.dirname(__FILE__)}/../../test/test_bot/integration/application_test.rb"]
-      t.warning = false
-    end
-
-    Rake::TestTask.new('effective_test_bot_environment' => 'test:prepare') do |t|
-      t.libs << 'test'
-      t.test_files = FileList["#{File.dirname(__FILE__)}/../../test/test_bot/integration/environment_test.rb"]
-      t.warning = false
-    end
-  end
-
 end

data/test/support/effective_test_bot_assertions.rb

@@ -17,16 +17,16 @@ module EffectiveTestBotAssertions
     assert assigns['current_user'].blank?, message || 'Expected @current_user to be blank when signed out'
   end
 
-  def assert_capybara_can_execute_javascript(message = "Expected capybara-webkit page.evaluate_script() to be successful")
+  def assert_can_execute_javascript(message = "Expected page.evaluate_script() to be successful")
     error = nil; result = nil;
 
     begin
-      result = page.evaluate_script("var js = 'javascript'; js;")
+      result = page.evaluate_script('1+1').to_s
     rescue => e
       error = e.message
     end
 
-    assert (result == 'javascript'), "#{message}. Error was: #{error}"
+    assert (result == '2'), "#{message}. Error was: #{error}"
   end
 
   def assert_jquery_present(message = "Expected jquery ($.fn.jquery) to be present")
@@ -55,14 +55,14 @@ module EffectiveTestBotAssertions
   end
 
   def assert_authorization(message = '(authorization) Expected authorized access')
-    if page.status_code == 403
+    if response_code == 403
       exception = access_denied_exception
 
       info = [
         "Encountered a 403 Access Denied",
         ("(cannot :#{exception['action']}, #{exception['subject']})" if exception.present?),
         "on #{page.current_path} as user #{user || 'no user'}.",
-        ("\nAdd assign_test_bot_access_denied_exception(exception) if defined?(EffectiveTestBot) to your ApplicationController's rescue_from block to gather more information." unless exception.present?),
+        ("\nAdd assign_test_bot_access_denied_exception(exception) if defined?(EffectiveTestBot) to the very bottom of your ApplicationController's rescue_from block to gather more information." unless exception.present?),
       ].compact.join(' ')
 
       assert false, "#{message}.\n#{info}"
@@ -70,7 +70,7 @@ module EffectiveTestBotAssertions
   end
 
   def assert_page_status(status = 200, message = '(page_status) Expected :status: HTTP status code')
-    assert_equal status, page.status_code, message.sub(':status:', status.to_s)
+    assert_equal status, response_code, message.sub(':status:', status.to_s)
   end
 
   def assert_current_path(path, message = '(current_path) Expected current_path to be :path:')
@@ -104,29 +104,16 @@ module EffectiveTestBotAssertions
   end
 
   def assert_no_js_errors(message = nil)
-    errors = page.driver.error_messages
-    assert errors.blank?, message || "(no_js_errors) Unexpected javascript error:\n#{errors.first.to_s}"
-  end
+    error = page.driver.browser.manage.logs.get(:browser).first # headless_chrome
+    error = error.message.gsub(/^http.+js \d+:\d+ /, '') if error.present?
 
-  def assert_no_unpermitted_params(message = "(no_unpermitted_params) Unexpected unpermitted params:\n:unpermitted_params:")
-    assert unpermitted_params.blank?, message.sub(':unpermitted_params:', unpermitted_params.to_s)
+    assert error.blank?, message || "(no_js_errors) Unexpected javascript error:\n#{error}"
   end
 
   def assert_no_flash_errors(message = "(no_flash_errors) Unexpected flash error:\n:flash_errors:")
     assert (!flash.key?('error') && !flash.key?('danger')), message.sub(':flash_errors:', flash.to_s)
   end
 
-  def assert_no_exceptions(message = "(no_exceptions) Unexpected rails server exception:\n:exception:")
-    # this file is created by EffectiveTestBot::Middleware when an exception is encountered in the rails app
-    file = File.join(Dir.pwd, 'tmp', 'test_bot', 'exception.txt')
-    return unless File.exist?(file)
-
-    exception = File.read(file)
-    File.delete(file)
-
-    assert false, message.sub(':exception:', exception)
-  end
-
   # This must be run after submit_form()
   # It ensures there are no HTML5 validation errors that would prevent the form from being submit
   # Browsers seem to only consider visible fields, so we will to

data/test/support/effective_test_bot_form_helper.rb

@@ -27,9 +27,7 @@ module EffectiveTestBotFormHelper
       with_raised_unpermitted_params_exceptions { click_submit(label, last: last, debug: debug) }
     end
 
-    assert_no_unpermitted_params unless test_bot_skip?(:no_unpermitted_params)
     assert_no_assigns_errors unless test_bot_skip?(:no_assigns_errors)
-    assert_no_exceptions unless test_bot_skip?(:exceptions)
     assert_authorization unless test_bot_skip?(:authorization)
     assert_page_status unless test_bot_skip?(:page_status)
 

data/test/support/effective_test_bot_screenshots_helper.rb

@@ -87,7 +87,7 @@ module EffectiveTestBotScreenshotsHelper
   # current_test_failure_path: destination for .gifs of failing tests
 
   def current_test_temp_path
-    @_current_test_temp_path ||= "#{Rails.root}/tmp/test_bot/#{current_test_name.parameterize}"
+    @_current_test_temp_path ||= "#{Rails.root}/tmp/test_bot/screenshots/#{current_test_name.parameterize}"
   end
 
   def current_test_failure_path
@@ -95,8 +95,7 @@ module EffectiveTestBotScreenshotsHelper
   end
 
   def current_test_failure_filename
-    # Match Capybara-screenshots format-ish
-    "#{current_test_name.parameterize}-failure-#{Time.now.strftime('%Y-%m-%d-%H-%M-%S')}.gif"
+    "failures_#{current_test_name}.gif"
   end
 
   # Where the tour animated gif ends up

data/test/support/effective_test_bot_test_helper.rb

@@ -51,15 +51,6 @@ module EffectiveTestBotTestHelper
     from_path != (to_path || page.current_path)
   end
 
-  def was_download?(filename = nil)
-    if filename.present?
-      page.response_headers['Content-Disposition'].to_s.include?('filename=') &&
-      page.response_headers['Content-Disposition'].to_s.include?(filename)
-    else
-      page.response_headers['Content-Disposition'].to_s.include?('filename=')
-    end
-  end
-
   # Calls capybara within do .. end if selector is present and bool is true
   def within_if(selector, bool = true, &block)
     (selector.present? && bool) ? within(selector) { yield } : yield
@@ -71,20 +62,26 @@ module EffectiveTestBotTestHelper
 
   # EffectiveTestBot includes an after_filter on ApplicationController to set an http header
   # These values are 'from the last page submit or refresh'
-  def flash
-    (JSON.parse(Base64.decode64(page.response_headers['Test-Bot-Flash'])) rescue {})
+  def response_code
+    page.evaluate_script('window.effective_test_bot.response_code')&.to_i
   end
 
-  def assigns
-    (JSON.parse(Base64.decode64(page.response_headers['Test-Bot-Assigns'])) rescue {})
+  def flash
+    page.evaluate_script('window.effective_test_bot.flash')
   end
 
-  def unpermitted_params
-    (JSON.parse(Base64.decode64(page.response_headers['Test-Bot-Unpermitted-Params'])) rescue [])
+  def assigns
+    page.evaluate_script('window.effective_test_bot.assigns')
   end
 
   def access_denied_exception
-    (JSON.parse(Base64.decode64(page.response_headers['Test-Bot-Access-Denied'])) rescue {})
+    return nil unless page.evaluate_script('window.effective_test_bot.access_denied').present?
+
+    {
+      'exception': page.evaluate_script('window.effective_test_bot.access_denied'),
+      'action': page.evaluate_script('window.effective_test_bot.action'),
+      'subject': page.evaluate_script('window.effective_test_bot.subject')
+    }
   end
 
 end

data/test/test_bot/{integration → system}/application_test.rb

@@ -1,10 +1,10 @@
-require 'test_helper'
+require 'application_system_test_case'
 
 # This gets run when we type `rake test:bot`
 # Scan through every route and run a test suite against it
 
 module TestBot
-  class ApplicationTest < ::Capybara::Rails::TestCase
+  class ApplicationTest < ApplicationSystemTestCase
     CRUD_ACTIONS = %w(index create new edit show update destroy) # Same order as resources :object creates them in
 
     class << self

data/test/test_bot/{integration → system}/environment_test.rb

@@ -1,7 +1,7 @@
-require "test_helper"
+require 'application_system_test_case'
 
 module TestBot
-  class EnvironmentTest < ::Capybara::Rails::TestCase
+  class EnvironmentTest < ApplicationSystemTestCase
     @@original_users_count = User.count
     let(:original_users_count) { @@original_users_count }
 
@@ -52,7 +52,7 @@ module TestBot
       user = User.new(email: 'unique@testbot.com', password: '!Password123', password_confirmation: '!Password123')
       user.username = 'unique-username' if user.respond_to?(:username)
       user.login = 'unique-login' if user.respond_to?(:login)
-      user.save(validate: false)
+      user.save!
 
       without_screenshots { sign_in_manually(user, '!Password123') }
       assert_signed_in("expected successful devise manual sign in with user created in this test.\nTry using one of the ActiveRecord shared_connection snippets in test/test_helper.rb")
@@ -60,7 +60,7 @@ module TestBot
 
     test '09: capybara can execute javascript' do
       visit root_path
-      assert_capybara_can_execute_javascript
+      assert_can_execute_javascript
     end
 
     test '10: jquery is present' do
@@ -79,5 +79,6 @@ module TestBot
         "expected action_mailer.default_url_options[:host] to be present.\nAdd config.action_mailer.default_url_options = { host: 'example.com' } to config/environments/test.rb"
       )
     end
+
   end
 end

data/test/test_botable/base_test.rb

@@ -7,11 +7,10 @@ module BaseTest
   def assert_page_normal(message = nil)
     return if test_bot_skip?(:normal)
 
-    assert_no_exceptions unless test_bot_skip?(:exceptions)
     assert_authorization unless test_bot_skip?(:authorization)
     assert_page_status unless test_bot_skip?(:page_status)
     assert_no_js_errors unless test_bot_skip?(:no_js_errors)
-    assert_page_title unless (test_bot_skip?(:page_title) || all('head').blank? || was_download?)
+    assert_page_title unless (test_bot_skip?(:page_title) || all('head').blank?)
   end
 
   private
@@ -53,7 +52,6 @@ module BaseTest
 
       visit(new_path)
 
-      assert_no_exceptions
       assert_authorization(hint)
       assert_page_status
 
@@ -65,7 +63,6 @@ module BaseTest
         fill_form(resource_attributes)
         submit_novalidate_form
 
-        assert_no_exceptions
         assert_authorization(hint)
         assert_page_status
       end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: effective_test_bot
 version: !ruby/object:Gem::Version
-  version: 0.7.0
+  version: 1.0.0
 platform: ruby
 authors:
 - Code and Effect
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-06-18 00:00:00.000000000 Z
+date: 2018-06-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -16,78 +16,36 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 3.2.0
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '5.2'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 3.2.0
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '5.2'
-- !ruby/object:Gem::Dependency
-  name: effective_resources
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
+        version: '5.1'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '5.1'
 - !ruby/object:Gem::Dependency
-  name: minitest
+  name: capybara
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: minitest-rails
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
+        version: '2.15'
+    - - "<"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '4.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: minitest-capybara
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
+        version: '2.15'
+    - - "<"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '4.0'
 - !ruby/object:Gem::Dependency
-  name: minitest-fail-fast
+  name: chromedriver-helper
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -101,7 +59,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: minitest-rails-capybara
+  name: selenium-webdriver
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -115,7 +73,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: minitest-reporters
+  name: effective_resources
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -129,7 +87,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: capybara
+  name: faker
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -143,21 +101,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: capybara-webkit
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 1.6.0
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 1.6.0
-- !ruby/object:Gem::Dependency
-  name: capybara-screenshot
+  name: minitest-fail-fast
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -171,7 +115,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: capybara-slow_finder_errors
+  name: minitest-reporters
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -198,22 +142,8 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
-- !ruby/object:Gem::Dependency
-  name: faker
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-description: A shared library of rails model & capybara-based feature tests that should
-  pass in every Rails application.
+description: A shared library of rails model & system tests that should pass in every
+  Rails application.
 email:
 - info@codeandeffect.com
 executables: []
@@ -224,12 +154,12 @@ files:
 - README.md
 - app/helpers/effective_test_bot_controller_helper.rb
 - app/helpers/effective_test_bot_mailer_helper.rb
+- config/application_system_test_case.rb
 - config/effective_test_bot.rb
 - config/test_helper.rb
 - lib/effective_test_bot.rb
 - lib/effective_test_bot/dsl.rb
 - lib/effective_test_bot/engine.rb
-- lib/effective_test_bot/middleware.rb
 - lib/effective_test_bot/version.rb
 - lib/generators/effective_test_bot/install_generator.rb
 - lib/tasks/effective_test_bot_tasks.rake
@@ -249,8 +179,8 @@ files:
 - test/support/effective_test_bot_minitest_helper.rb
 - test/support/effective_test_bot_screenshots_helper.rb
 - test/support/effective_test_bot_test_helper.rb
-- test/test_bot/integration/application_test.rb
-- test/test_bot/integration/environment_test.rb
+- test/test_bot/system/application_test.rb
+- test/test_bot/system/environment_test.rb
 - test/test_botable/base_test.rb
 - test/test_botable/crud_test.rb
 - test/test_botable/devise_test.rb
@@ -281,6 +211,6 @@ rubyforge_project:
 rubygems_version: 2.4.5.1
 signing_key: 
 specification_version: 4
-summary: A shared library of rails model & capybara-based feature tests that should
-  pass in every Rails application.
+summary: A shared library of rails model & system tests that should pass in every
+  Rails application.
 test_files: []

data/lib/effective_test_bot/middleware.rb

@@ -1,40 +0,0 @@
-# Watch for any rails server exceptions and write the stacktrace to ./tmp/test_bot/exception.txt
-# This file is checked for by assert_no_exceptions
-
-module EffectiveTestBot
-  class Middleware
-    def initialize(app)
-      @app = app
-    end
-
-    def call(env)
-      begin
-        @app.call(env)
-      rescue Exception => exception
-        begin
-          save(exception)
-        rescue => e
-          puts "TestBotError: An error occurred while attempting to save a rails server exception: #{e.message}"
-        end
-
-        raise exception
-      end
-    end
-
-    def save(exception)
-      lines = [exception.message] + exception.backtrace.first(EffectiveTestBot.backtrace_lines)
-
-      dir = File.join(Dir.pwd, 'tmp', 'test_bot')
-      file = File.join(dir, 'exception.txt')
-
-      Dir.mkdir(dir) unless File.exist?(dir)
-      File.delete(file) if File.exist?(file)
-
-      File.open(file, 'w') do |file|
-        file.write "================== Start server exception ==================\n"
-        lines.each { |line| file.write(line); file.write("\n") }
-        file.write "=================== End server exception ===================\n"
-      end
-    end
-  end
-end