nruth

# load into test setup after `require 'capybara/rails'`

# some sources for below flags and profile settings
# https://stackoverflow.com/questions/43143014/chrome-is-being-controlled-by-automated-test-software/43145088
# https://sqa.stackexchange.com/questions/26051/chrome-driver-2-28-chrome-is-being-controlled-by-automated-test-software-notif
# http://stackoverflow.com/questions/12211781/how-to-maximize-window-in-chrome-using-webdriver-python
# update sources for new Options object
# https://github.com/SeleniumHQ/selenium/wiki/Ruby-Bindings
# https://github.com/teamcapybara/capybara/blob/master/lib/capybara/selenium/driver.rb
begin

nruth

# -*- encoding : utf-8 -*-
module PayStripeHelpers
  # must be used with driver: :selenium (or :sauce?)
  def pay_stripe
    sleep(0.7) # wait for the js to create the popup in response to pressing the button
    within_frame 'stripe_checkout_app' do # must be selenium
      # fill_in 'card_number', with: '4242424242424242' no longer works
      4.times {page.driver.browser.find_element(:id, 'card_number').send_keys('4242')}

      # fill_in 'cc-exp', with: '5/2018' no longer works

nruth

#!/usr/bin/env ruby
require 'fileutils'
extend FileUtils

cmd1 = "tell application \"System Events\" to tell process \"Terminal\" to keystroke \"t\" using command down"
cmd2 = "tell application \"Terminal\" to do script \"cd #{pwd}\" in the front window"
`osascript -e '#{cmd1}' -e '#{cmd2}'`

nruth

# Let's assume you're driving Capybara in both RSpec request specs & Cucumber, 
# for example you're using Cucumber as a design/documentation tool, and RSpec 
# for the more boring integration tests.

# You don't want to duplicate your click-this-click-that helpers to e.g. 
# log_in(username, password). 
# You may also have model state setup code which can be shared/reused.

# Where can it go? How can it be loaded? I've been using the following approach:
#

nruth

class Tests
  SUBTESTS = %w(Abstract Decision Quantitative Verbal)
end

describe Tests do

  describe "before assigning @ - " do
    describe "this doesn't work because the loops are all at the same describe level (the befores override one another)" do
      Tests::SUBTESTS.each do |test|
        before(:each) do

nruth

RSpec.configure do |config|
  config.filter_run_excluding :show_me_the_pages unless ENV["SHOW_ME_THE_PAGES"]
end



class Screenshots
  include Capybara::DSL
  attr_accessor :resolutions
  attr_accessor :output_path

nruth

Then /^show me the cookies!$/ do
  driver = Capybara.current_session.driver
  case driver
  when Capybara::Driver::Selenium
    announce_selenium_cookies(Capybara.current_session.driver.browser)
  when Capybara::Driver::RackTest
    announce_rack_test_cookies(get_rack_test_cookie_jar)
  else 
    raise "unsupported driver, use rack::test or selenium/webdriver"
  end

nruth

# pods aren't really a thing going forward, and come up as a problem during paid code reivews
# there is/was an alternative in the works to do with modules, but it's best to be on the old
# default ember-cli directory structure so that any new codemods can work

require 'fileutils'

app_pods = "app/pods"

puts "Shucking Routes"
routes = Dir.glob(File.join(app_pods, "**", "route.js"))

nruth

If you start to see something like this, e.g. on Heroku since they installed the postgres 9.5 client libraries on their dynos

/usr/lib/postgresql/9.5/bin/pg_dump: invalid option -- 'i'
Try "pg_dump --help" for more information.
rake aborted!
Error dumping database
/app/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.4/lib/active_record/tasks/postgresql_database_tasks.rb:55:in `structure_dump'

nruth

TracePoint.trace(:c_call) do |tp|
  # the various methods on tp tell you where warn is defined, but we want to know about the call stack, 
  # in particular the test code that the test library didn't like and decided to warn us about, 
  # so let's Array#grep the caller strings, filtering out the rspec library lines
  if tp.method_id == :warn
    app_lines = caller(0).grep(%r{enough-of-your-app-code-path-to-match/})
    app_lines_without_reporter = app_lines.grep_v(/name-of-your-rspec-support-file-holding-this-code/)
    p app_lines_without_reporter.join("\n")
    p
  end