effective_test_bot 0.4.6 → 0.4.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0b7f79228e53f919d49e05e1c4664c154e8852f1
-  data.tar.gz: 23d86e7bffe2f127072aa2a27254e2420305526d
+  metadata.gz: 050059046b219c8b63e06bed237a2af8330bbd74
+  data.tar.gz: 5ab3fb4a52857df4f5a158207fdc16f5fb5eccc7
 SHA512:
-  metadata.gz: 001cada50f2fe9ad01c38607d7a42ac40176cb69dc09897e5874c50819c9e28ef51bdda5759455db13e722219dec2a13db1f6ee4d8dd75cdf5ef36c98ac49496
-  data.tar.gz: e0639c6e7c1a233ac3e98dab49290814cffe7d8668173d683bc2a64c04ecb63264377510ad92bd3c630de6c72b75958ad123286b4ef7fecf8127bb972d6013c2
+  metadata.gz: 153ff53a0aaea5cdc8df869c479cb6202e2bc422713cb9bc278ec704d233e8aac52faf58a4b98b7f601a2d268127b58d9805f8a57f967fbaecb2aa047c6680d1
+  data.tar.gz: 6ef150344ff12ace02a5717611b8f537540061653141d375ed5c79ddad6f69f87b3b7d8669d4ba639582d9bfc8ff94cad51c10322e693b57f0ca9f55c9dd9fc0

data/README.md

@@ -1,18 +1,37 @@
 # Effective TestBot
 
-A shared library of rails model & capybara-based feature tests that should pass in every Rails application.
+Stop testing and start test botting.
 
-Also provides a one-liner installation & configuration of minitest and capybara test environment.
+A minitest library of capybara-webkit based feature tests that should pass in every Ruby on Rails application.
 
-Rails 3.2.x and 4.x
+Adds many additional minitest assertions and capybara quality of life helper functions.
 
+Provides a curated set of minitest/capybara/rails testing gems and a well configured `test_helper.rb` minitest file.
+
+Includes a rake task 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.
+
+Provides a DSL of class and instance level 1-liners that run entire test suites, checking many assertions all at once.
+
+Autosaves an animated gif for any failing test.
+
+Run `rake test:bot` to automatically check every route in your application against an appropriate test suite, without writing any code.
+
+Automatically fills forms with appropriate pseudo-random input, and checks for all kinds of errors and omissions along the way.
+
+Turn on tour mode to automatically generate animated gifs of every part of your website.
+
+Makes sure everything actually works.
 
 ## Getting Started
 
-Add to your Gemfile:
+Make sure your site is using [devise](https://github.com/plataformatec/devise) and that your application javascript includes [jQuery](http://jquery.com/) and rails' [jquery_ujs](https://github.com/rails/jquery-ujs).
 
 ```ruby
-gem 'effective_test_bot'
+group :test do
+  gem 'effective_test_bot'
+end
 ```
 
 Run the bundle command to install it:
@@ -21,99 +40,250 @@ Run the bundle command to install it:
 bundle install
 ```
 
-Then run the generator:
+Install the configuration file:
 
-```ruby
+```console
 rails generate effective_test_bot:install
 ```
 
-The above command will first invoke the default `minitest` installation tasks, if they haven't already been run.
+The generator will run `minitest:install` if minitest is not already present and create an initializer file which describes all configuration options.
+
+Fixture or seed one user:
 
-It will then copy the packaged `test_helper.rb` that matches this gem author's opinionated testing environment.
+effective_test_bot requires that at least one user -- ideally a fully priviledged admin type user -- be available in the testing environment.
 
-Run the test suite with:
+* There are future plans to make this better.  Right now `rake test:bot` just runs everything as one user.  There really isn't support for 'this user should not be able to'. yet.
+
+As per the `test/test_helper.rb` default file, when minitest and/or effective_test_bot starts, following tasks are run:
 
 ```ruby
-bundle exec rake test:bot
-bundle exec rake test:bot:environment
+# Rails default task, load fixtures from test/fixtures/*.yml (including users.yml if it exists)
+rake db:fixtures:load
+
+# Rails default task, loads db/seeds.rb
+rake db:seed
+
+# Added by effective_test_bot.  loads test/fixtures/seeds.rb. 'cause screw yaml.
+rake test:load_fixture_seeds
 ```
 
-You should now see multiple -- hopefully passing -- tests that you didn't write!
+Your initial user may be created by any of the above 3 tasks.
 
-## TODO
+Test that your testing environment is set up correctly:
 
-Document this gem
+Run `rake test:bot:environment` and make sure all the tests pass.
 
-Minitest:
+You now have effective_test_bot configured and you're ready to go.
 
-rake test TEST=test/integration/clinic_assets_test.rb
+# How to use this gem
 
-TestBot:
+Effective TestBot is a 3-layered cake of testing deliciousness.
 
-rake test:bot TEST=posts
-rake test:bot TEST=posts#index
-rake test:bot TEST=
+The bottom layer consists of advanced individual minitest assertions and capybara quality of life helper functions.
 
-Excepts will always work and be accounted for in test:bot
-Definign TEST= works with test names 'documents#new' or 'documents' or 'something_path' but not with 'flash' assertions
+The middle layer is a meta testing DSL -- 1-liners for you to use in your regular minitest tests that run entire test suites (10-50+ assertions) against a page or controller.
 
+The final layer builds on the bottom two, run `rake test:bot` to scan every route in your application and choose an appropriate test suite to run.
 
-    # config.except = [
-    #   'flash',
-    #   'users#show',
-    #   'users#create_invalid' => ['path', 'page_title'],
-    #   'users#create_invalid' => 'no_unpermitted_params',
-    #   'report_total_allocation_index_path'
-    #   'documents#destroy flash'
-    # ]
+## Minitest Assertions
 
+The following assertions are added for use in any minitest & capybara integration test:
 
-require 'test_helper'
+- `assert_signed_in` visits the devise `new_user_session_path` and checks for the `devise.failure.already_authenticated` content
+- `assert_signed_out` visits the devise `new_user_session_path` and checks for absense of the `devise.failure.already_authenticated` content
+- `assert_page_title` makes sure there is an html <title></title> present
+- `assert_submit_input` makes sure there is an input[type='submit'] present
+- `assert_page_status` checks for a given http status, default 200.
+- `assert_current_path(path)` asserts the current page path
+- `assert_redirect(from_path)` optionally with to_path, makes sure the current page path is not from_path
+- `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_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_jquery_ujs_disable_with` makes sure all input[type=submit] elements on the page have the data-disable-with property set
+- `assert_flash` optionally with the desired :success, :error key and/or message, makes sure the flash is set
+- `assert_assigns` asserts a given rails view_assigns object is present
+- `assert_no_assigns_errors` use after a form submit to make sure your assigned rails object has no errors.  Prints out any errors if they exist.
+- `assert_assigns_errors` use after an intentionally invalid form submit to make sure your assigned rails object has errors, or a specific error.
 
-class UsersTest < ActionDispatch::IntegrationTest
-  # The Create and Update action return to /members/12345 instead of /users/12345 when failing validation
-  # This is a side effect of working in the same namespace as devise
-  crud_test(User, User.find_by_email('admin@agilestyle.com'), except: :show, skip: {create_invalid: :path, update_invalid: :path})
-end
+## Capybara Extras
+
+The following quality of life helpers are added for use in any minitest & capybara integration test:
+
+### fill_form
+
+Finds all the input, select and textarea form fields on the current page and fills them with pseudo-random appropriate values.
+
+Detects names, addresses, start and end dates, telephone numbers, postal and zip codes, file, price, email, numeric, password and password confirmation fields. Probably more.
+
+Will only fill visible fields that are currently visible and not disabled.
+
+If a selection made in one field changes the visibility/disabled of fields later in the form, those fields will be properly filled.
 
+It works with the [cocoon](https://github.com/nathanvda/cocoon), [select2](https://select2.github.io/) and [effective_assets](https://github.com/code-and-effect/effective_assets) gems.
+
+It will click through bootstrap tabs and fill them left-to-right one tab at a time.
+
+You can pass a Hash of 'fills' to specify specific input values:
+
+```ruby
 require 'test_helper'
 
-class SettingTest < ActionDispatch::IntegrationTest
-  crud_test(Setting, User.first, only: [:new, :create])
+class PostTest < ActionDispatch::IntegrationTest
+  test 'creating a new post' do
+    visit new_post_path
+    fill_form(:title => 'A Cool Post', 'author.last_name' => 'Smith')
+    submit_form
+  end
 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
+```
+
+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.
+
+The `min` and `max` html properties are considered when filling in any numeric field -- the fill value will always be within the specified range.
+
+If there are 2 or more numeric inputs that end with the same jquery selector, the fields will be filled so that their sum will match the html `max` value.
+
+You can scope the fill_form to a particular area of the page by using the regular capybara `within` `do..end` block
+
+### submit_form
+
+As well as just click on the `input[type='submit']` button (or optional label), this helper also checks:
+- `assert_no_html5_form_validation_errors`
+- `assert_jquery_ujs_disable_with`
+- `assert_no_unpermitted_params`
+
+### other helpers
+
+- `submit_novalidate_form` will use javascript to disable all required fields, and submit a form without client side validation.
+- `clear_form` clears all form fields, probably used before `submit_novalidate_form` to test invalid form submissions.
+- `sign_in(user)` optionally with user, signs in via `Warden::Test::Helpers` hacky login skipping method.
+- `sign_in_manually(user, password)` visits the devise `new_user_session_path` and signs in via the form
+- `sign_up` visits the devise `new_user_registration_path` and signs up as a new user.
+- `as_user(user) do .. end` yields a block between `sign_in`, and `logout`
+- `synchronize!` should fix any timing issues waiting for capybara 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.
+
+## Capybara Super Extras
+
+So the problem with running integration tests with capybara-webkit is that it's a real full black-box integration test.
+
+Capybara runs in a totally separate process.  It knows nothing about your rails app.  You can't get access to any of the rails internal state. All you can test is html, javascript and urls. That really sucks.
 
+effective_test_bot mixes in a rails controller include and does a bit of http header hackery to make available to capybara the internal rails state values that are just so handy.
+
+The following are refreshed on each page change, and are available to check anywhere in your tests.
+
+- `flash` a Hash representation of the current page's flash
+- `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, Numeric objects.  Does not serialize anything else, but sets a symbol `assigns[key] == :present_but_not_serialized`.
+- `exceptions` an Array with the exception message and a stacktrace.
+- `unpermitted_params` an Array of any unpermitted paramaters that were encountered by the last request
+
+- `save_test_bot_screenshot` saves a screenshot of the current page to be added to the current test's animated gif (see screenshots and tour mode below).
+
+## Test Bot DSL Methods
+
+All of the following DSL methods use the assertions and capybara extras to build an entire test suite that runs against a given page or controller action.
+
+Right now the `crud_test` method is by far the most mature, with the other methods having had less development time.
+
+Each DSL method has a class level `x_test` and an instance level `x_action_test` version of each.
+
+```ruby
 require 'test_helper'
 
-class PhysiciansTest < ActionDispatch::IntegrationTest
-  page_test(:user_settings_path, User.first)
-  page_test(:user_settings_path, User.first)
-  page_test(:user_settings_path, User.first)
-  crud_test(Physician, User.first, except: :show)
-  crud_test('physicians', User.first, except: :show)
+class PostsTest < ActionDispatch::IntegrationTest
+  page_test(:posts_path, User.first)  # Runs the page_test test suite against posts_path (class level) as User.first
 
-  test 'another action' do
-    crud_action_test(:new, Physician, User.first)
+  # Does the same thing.
+  # Runs the page_test suite against posts_path (instance level) as User.first
+  test 'my posts test' do
+    page_action_test(:posts_path, User.first)
   end
 end
+```
 
+### Skipping assertions and tests
 
-, input_html: {'data-test-bot-skip': true}
+Each of these DSL test suite methods are designed to assert an expected standard rails behaviour.
 
+But sometimes a developer has a good reason for deviating from what is considered standard; therefore, each individual assertion is skippable.
 
+When an assertion fails, the minitest output will look something like:
 
+```console
+crud_test: (users#update_invalid)                               FAIL (3.74s)
 
-## Fixtures
+Minitest::Assertion: (path) Expected current_path to match resource #update path.
+  Expected: "/users/562391275"
+  Actual: "/members/562391275"
+  /Users/matt/Sites/effective_test_bot/test/test_botable/crud_test.rb:155:in `test_bot_update_invalid_test'
+```
 
-TODO
+The `(path)` is the name of the specific assertion that failed.
+
+The expectation is that when submitting an invalid form at `/users/562391275/edit` we should be returned to the update action url `/users/562391275`, but in this totally reasonable but not-standard case we are redirected to `/members/562391275` instead.
 
-users.yml:
+You can skip this specific assertion by adding it to the `app/config/initializers/effective_test_bot.rb` file:
 
-```yaml
-normal:
-  email: 'normal@agilestyle.com'
-  encrypted_password: <%= Devise::Encryptor.digest(User, 'password') %>
+```ruby
+EffectiveTestBot.setup do |config|
+  config.except = [
+    'users#create_invalid path',  # Skips the path assertion for just the users#create_invalid test
+    'path'                        # Skips the path assertion entirely in all tests
+  ]
+end
 ```
 
+There is support for skipping individual assertions as well as entire tests.
+
+Please see the installed effective_test_bot.rb initializer file for a full description of all options.
+
+### crud_test
+
+TODO
+
+### devise_test
+
+TODO
+
+### page_test
+
+TODO
+
+### member_test
+
+TODO
+
+### redirect_test
+
+TODO
+
+### wizard_test
+
+TODO
+
+## Automated Testing / Rake tasks
+
+TODO
+
+## Screenshots and Animated Gifs
+
+TODO
+
+### Tour mode
+
+TODO
+
 
 ## License
 

data/lib/effective_test_bot.rb

@@ -7,6 +7,7 @@ module EffectiveTestBot
   mattr_accessor :screenshots
   mattr_accessor :autosave_animated_gif_on_failure
   mattr_accessor :tour_mode
+  mattr_accessor :tour_mode_extreme
   mattr_accessor :animated_gif_delay
   mattr_accessor :animated_gif_background_color
 
@@ -60,11 +61,20 @@ module EffectiveTestBot
     end
   end
 
+  # form_filler will take a screenshot after every form field is filled
+  def self.tour_mode_extreme?
+    if ENV['TOUR'].present?
+      ['extreme', 'debug'].include?(ENV['TOUR'].to_s.downcase)
+    else
+      screenshots && ['extreme', 'debug'].include?(tour_mode.to_s)
+    end
+  end
+
   def self.tour_mode_verbose?
     if ENV['TOUR'].present?
-      ['verbose', 'debug'].include?(ENV['TOUR'].to_s.downcase)
+      ['extreme', 'verbose', 'debug'].include?(ENV['TOUR'].to_s.downcase)
     else
-      screenshots && ['verbose', 'debug'].include?(tour_mode.to_s)
+      screenshots && ['extreme', 'verbose', 'debug'].include?(tour_mode.to_s)
     end
   end
 

data/lib/effective_test_bot/version.rb

@@ -1,3 +1,3 @@
 module EffectiveTestBot
-  VERSION = '0.4.6'.freeze
+  VERSION = '0.4.7'.freeze
 end

data/lib/generators/effective_test_bot/install_generator.rb

@@ -22,9 +22,7 @@ module EffectiveTestBot
         puts "files with those packaged inside the effective_test_bot gem."
         puts ""
         puts "If you have very specific existing minitest configuration,"
-        puts "you may want to skip (press 'n') to the following overwrites"
-        puts "and refer to the GitHub documentation for this gem:"
-        puts "https://github.com/code-and-effect/effective_test_bot"
+        puts "you should ensure it's under version control so you can revert if needed"
         puts ""
         puts "Otherwise, press 'Y' to all the following prompts to automatically configure"
         puts "minitest-rails and capybara-webkit based effective_test_bot test coverage"
@@ -41,8 +39,9 @@ module EffectiveTestBot
 
       def thank_you
         puts "Thanks for using EffectiveTestBot"
-        puts "First make sure your test environment is correctly configured by running 'rake test:bot:environment'"
-        puts "Run tests with 'rake test:bot'"
+        puts "Make sure you create a user in your db/seeds.rb, test/fixtures/users.yml, or test/fixtures/seeds.rb"
+        puts "Run `rake test:bot:environment` once to ensure the testing environment is correctly configured"
+        puts "Test your app with 'rake test:bot'"
       end
     end
   end

data/lib/generators/templates/effective_test_bot.rb

@@ -39,7 +39,7 @@ if Rails.env.test?
     # 100 equals 1 second. (a bit on the slow side, but suitable for a demo)
     config.animated_gif_delay = 100
 
-    # Shorter than maximum height animaged gif frames have their
+    # Shorter than maximum height animated gif frames have their
     # bottom area filled by this color
     # For best appearance, have this match your site's background color
     config.animated_gif_background_color = 'white'

data/lib/tasks/effective_test_bot_tasks.rake

@@ -67,6 +67,14 @@ namespace :test do
     end
   end # /namespace bot
 
+  desc 'loads test/fixtures/seeds.rb'
+  task :load_fixture_seeds => :environment do
+    seeds = "#{Rails.root}/test/fixtures/seeds.rb"
+    load(seeds) if File.exists?(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
   Rails::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"]
@@ -77,10 +85,4 @@ namespace :test do
     t.test_files = FileList["#{File.dirname(__FILE__)}/../../test/test_bot/integration/environment_test.rb"]
   end
 
-  desc 'loads test/fixtures/seeds.rb'
-  task :load_fixture_seeds => :environment do
-    seeds = "#{Rails.root}/test/fixtures/seeds.rb"
-    load(seeds) if File.exists?(seeds)
-  end
-
 end

data/test/support/effective_test_bot_assertions.rb

@@ -11,6 +11,26 @@ module EffectiveTestBotAssertions
     assert page.has_selector?('form#new_user'), message || '(signed_out) Expected new_user form to be present'
   end
 
+  def assert_capybara_can_execute_javascript(message = "Expected capybara-webkit page.evaluate_script() to be successful")
+    error = nil; result = nil;
+
+    begin
+      result = page.evaluate_script("var js = 'javascript'; js;")
+    rescue => e
+      error = e.message
+    end
+
+    assert (result == 'javascript'), "#{message}. Error was: #{error}"
+  end
+
+  def assert_jquery_present(message = "Expected jquery ($.fn.jquery) to be present")
+    assert((page.evaluate_script('$.fn.jquery') rescue '').length > 0, message)
+  end
+
+  def assert_jquery_ujs_present(message = "Expected rails' jquery_ujs ($.rails) to be present")
+    assert((page.evaluate_script('$.rails') rescue '').length > 0, message)
+  end
+
   def assert_page_title(title = :any, message = '(page_title) Expected page title to be present')
     return if was_download? # If this was a download, it correctly won't have a page title
 

data/test/support/effective_test_bot_form_filler.rb

@@ -45,10 +45,18 @@ module EffectiveTestBotFormFiller
   def fill_form_fields(fills = {})
     fills = HashWithIndifferentAccess.new(fills) unless fills.kind_of?(HashWithIndifferentAccess)
 
+    save_test_bot_screenshot
+
     # Support for the cocoon gem
     all('a.add_fields[data-association-insertion-template]').each do |field|
       next if skip_form_field?(field)
-      2.times { field.click(); save_test_bot_screenshot }
+
+      if EffectiveTestBot.tour_mode_extreme?
+        2.times { field.click(); save_test_bot_screenshot }
+      else
+        2.times { field.click() }
+        save_test_bot_screenshot
+      end
     end
 
     all('input,select,textarea', visible: false).each do |field|
@@ -60,11 +68,19 @@ module EffectiveTestBotFormFiller
         field.set(value_for_field(field, fills))
       when 'select'
         if field['class'].to_s.include?('select2') # effective_select
-          page.execute_script("try { $('select##{field['id']}').select2('open'); } catch(e) {};")
-          save_test_bot_screenshot
+          if EffectiveTestBot.tour_mode_extreme?
+            page.execute_script("try { $('select##{field['id']}').select2('open'); } catch(e) {};")
+            save_test_bot_screenshot
+          end
         end
 
         field.select(value_for_field(field, fills), match: :first)
+
+        if field['class'].to_s.include?('select2') # effective_select
+          if EffectiveTestBot.tour_mode_extreme?
+            page.execute_script("try { $('select##{field['id']}').select2('close'); } catch(e) {};")
+          end
+        end
       when 'input_file'
         if field['class'].to_s.include?('asset-box-uploader-fileinput')
           upload_effective_asset(field, value_for_field(field, fills))
@@ -78,8 +94,13 @@ module EffectiveTestBotFormFiller
         raise "unsupported field type #{[field.tag_name, field['type']].compact.join('_')}"
       end
 
-      save_test_bot_screenshot unless skip_field_screenshot
+      if EffectiveTestBot.tour_mode_extreme?
+        save_test_bot_screenshot unless skip_field_screenshot
+      end
     end
+
+    save_test_bot_screenshot
+
   end
 
   # Generates an appropriately pseudo-random value for the given field
@@ -241,7 +262,7 @@ module EffectiveTestBotFormFiller
         within("#asset-box-input-#{uid}") do
           within('.uploads') do
             while (first('.upload').present? rescue false) do
-              save_test_bot_screenshot
+              save_test_bot_screenshot if EffectiveTestBot.tour_mode_extreme?
               sleep(0.5)
             end
           end

data/test/support/effective_test_bot_form_helper.rb

@@ -45,7 +45,8 @@ module EffectiveTestBotFormHelper
       end
 
       begin
-        field.set(''); save_test_bot_screenshot
+        field.set('');
+        save_test_bot_screenshot if EffectiveTestBot.tour_mode_extreme?
       rescue => e; end
     end
 

data/test/support/effective_test_bot_login_helper.rb

@@ -9,12 +9,14 @@ module EffectiveTestBotLoginHelper
     user.kind_of?(String) ? login_as(User.find_by_email!(user)) : login_as(user)
   end
 
-  def sign_in_manually(email, password)
+  def sign_in_manually(user_or_email, password = nil)
     visit new_user_session_path
 
+    email = (user_or_email.respond_to?(:email) ? user_or_email.email : user_or_email)
+
     within('form#new_user') do
       fill_form(email: email, password: password)
-      submit_form
+      submit_novalidate_form
     end
   end
 
@@ -23,7 +25,7 @@ module EffectiveTestBotLoginHelper
 
     within('form#new_user') do
       fill_form(email: email, password: password, password_confirmation: password)
-      submit_form
+      submit_novalidate_form
     end
 
     User.find_by_email(email)

data/test/test_bot/integration/environment_test.rb

@@ -7,7 +7,7 @@ module TestBot
 
     let(:email) { 'unique@testbot.com' }
     let(:password) { '!Password123' }
-    let(:create_user!) { User.new(email: email, password: password, password_confirmation: password).save(validate: false) }
+    let(:username) { 'test_bot_user' }
 
     def self.test_order
       :alpha
@@ -18,20 +18,20 @@ module TestBot
     end
 
     test '02: all fixtures and seeds valid' do
+      tables = ActiveRecord::Base.connection.tables
+
       ActiveRecord::Base.descendants.each do |model|
-        begin
-          (model.unscoped.all rescue []).each do |resource|
-            assert resource.valid?, "fixture or seed data is invalid (#{model.to_s} id=#{resource.id} #{resource.errors.full_messages.join(', ')})"
-          end
-        rescue ActiveRecord::StatementInvalid
-          ; # Not entirely sure why I'm getting this error
+        next unless (model.respond_to?(:table_name) && tables.include?(model.table_name))
+
+        (model.unscoped.all rescue []).each do |resource|
+          assert resource.valid?, "fixture or seed data is invalid (#{model.to_s} id=#{resource.id} #{resource.errors.full_messages.join(', ')})"
         end
       end
     end
 
     # I could remove this if sign_in checks for and creates a user with devise or not
     test '03: at least one user is seeded' do
-      assert (User.all.count > 0), 'please create at least 1 seed or fixture user for effective_test_bot to function'
+      assert (User.count > 0), 'please create at least 1 seed or fixture user for effective_test_bot to function'
     end
 
     test '04: activerecord can create a user' do
@@ -43,37 +43,52 @@ module TestBot
       assert_environment_normal
     end
 
-    test '06: capybara can sign up a user' do
+    test '06: capybara can execute javascript' do
+      visit root_path
+      assert_capybara_can_execute_javascript
+    end
+
+    test '07: jquery is present' do
+      visit root_path
+      assert_jquery_present
+    end
+
+    test '08: rails jquery_ujs is present' do
+      visit root_path
+      assert_jquery_ujs_present
+    end
+
+    test '09: capybara can sign up a user' do
       user = sign_up()
-      assert user.kind_of?(User)
+      assert user.kind_of?(User), "expected to create a new user after submitting sign up form at #{new_user_registration_path}"
 
       assert_equal (original_users_count + 1), User.count
       assert_signed_in
     end
 
-    test '07: database and session have reset' do
+    test '10: database and session have reset' do
       assert_signed_out
       assert_environment_normal
     end
 
-    test '08: capybara can login_as via warden test helper' do
+    test '11: capybara can login_as via warden test helper' do
       create_user!
       sign_in(email)
       assert_signed_in
     end
 
-    test '09: database and session have reset' do
+    test '12: database and session have reset' do
       assert_signed_out
       assert_environment_normal
     end
 
-    test '10: capybara can sign in manually' do
+    test '13: capybara can sign in manually' do
       create_user!
       sign_in_manually(email, password)
       assert_signed_in
     end
 
-    test '11: database and session have reset' do
+    test '14: database and session have reset' do
       assert_signed_out
       assert_environment_normal
     end
@@ -88,5 +103,13 @@ module TestBot
       assert assigns[:current_user].blank?, 'Expected current_user to be blank'
     end
 
+    def create_user!
+      user = User.new(email: email, password: password, password_confirmation: password)
+      user.username = username if user.respond_to?('username=')
+      user.login = username if user.respond_to?('login=')
+
+      user.valid? ? user.save : user.save(validate: false)
+    end
+
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: effective_test_bot
 version: !ruby/object:Gem::Version
-  version: 0.4.6
+  version: 0.4.7
 platform: ruby
 authors:
 - Code and Effect
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-10-21 00:00:00.000000000 Z
+date: 2015-11-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails