Minitest Automated Testing

Minitest is a very fast unit testing framework which supports TDD, BDD, mocking and benchmarking.


To begin, please make sure you have Minitest installed on your system:

$ gem install minitest


Example code

require 'rubygems'
require 'minitest/autorun'
require 'selenium-webdriver'

class GoogleTest < MiniTest::Test
  def setup
    url = "https://key:secret@hub.testingbot.com/wd/hub"
    @driver = Selenium::WebDriver.for(:remote, :url => url)
  end

  def test_post
    @driver.navigate.to "http://www.google.com"
    element = @driver.find_element(:name, 'q')
    element.send_keys "TestingBot"
    element.submit
    assert_equal(@driver.title, "TestingBot - Google Search")
  end

  def teardown
    @driver.quit
  end
end

Configuring capabilities

To run your existing tests on TestingBot, your tests will need to be configured to use the TestingBot remote machines. If the test was running on your local machine or network, you can simply change your existing test like this:


Before
driver = Selenium::WebDriver.for :firefox

After
driver = Selenium::WebDriver.for(:remote,
  :url => "https://API_KEY:API_SECRET@hub.testingbot.com/wd/hub",
  :desired_capabilities => caps)


Specifying the operating system, browser and version



To let TestingBot know on which browser/platform you want to run your test on, you need to specify the browsername, version, OS and other optional options in the capabilities field.


driver = Selenium::WebDriver.for(:remote,
  :url => "https://API_KEY:API_SECRET@hub.testingbot.com/wd/hub",
  :desired_capabilities => caps)

To see how to do this please select a combination of browser version and platform in the drop-down menus below

1. Select a Platform
2. Select a Browser


Testing Internal/Staged Websites

We've built TestingBot Tunnel, to provide you with a secure way to run tests against your staged/internal webapps.
Please see our TestingBot Tunnel documentation for more information about this easy to use tunneling solution.


The example below shows how to easily run a Minitest with our Tunnel:


1. Download our tunnel and start the tunnel:

java -jar testingbot-tunnel.jar key secret

2. Adjust your test: instead of pointing to 'hub.testingbot.com/wd/hub' like the example above - change it to point to your tunnel's IP address.
Assuming you run the tunnel on the same machine you run your tests, change to 'localhost:4445/wd/hub'. localhost is the machine running the tunnel, 4445 is the default port of the tunnel.


This way your test will go securily through the tunnel to TestingBot and back:


require 'rubygems'
require 'minitest/autorun'
require 'selenium-webdriver'

class GoogleTest < MiniTest::Test
  def setup
    url = "http://key:secret@localhost:4445/wd/hub"
    @driver = Selenium::WebDriver.for(:remote, :url => url)
  end

  def test_post
    @driver.navigate.to "http://www.google.com"
    element = @driver.find_element(:name, 'q')
    element.send_keys "TestingBot"
    element.submit
    assert_equal(@driver.title, "TestingBot - Google Search")
  end

  def teardown
    @driver.quit
  end
end

Other Options

We offer many other test options, for example: disable video recording, specifying a custom Firefox Profile, loading Chrome/Firefox/Safari extensions, running an executable before your test starts, uploading files, ...
See our list of test options for a full list of options to customize your tests.

Parallel Testing

Parallel Testing means running the same test, or multiple tests, simultaneously. This greatly reduces your total testing time.

You can run the same tests on all different browser configurations or run different tests all on the same browser configuration.
TestingBot has a large grid of machines and browsers, which means you can use our service to do efficient parallel testing. It is one of the key features we provide to greatly cut down on your total testing time.


Parallel Testing Example

The example below demonstrates how you can easily run tests simultaneously in a variety of browsers.


Create a browsers.json file with the list of browsers you want to use to run tests in parallel:

[
    {
      "browserName": "firefox",
      "version": "latest",
      "platform": "LINUX"
    },
    {
      "browserName": "safari",
      "version": "9",
      "platform": "CAPITAN"
    },
    {
      "browserName": "chrome",
      "version": "latest",
      "platform": "WIN7"
    }
  ]

Now we need to create the test and use environment variables which we will pass to the test script.


require 'rubygems'
  require 'minitest/autorun'
  require 'selenium-webdriver'

  class GoogleTest < MiniTest::Test
    def setup
      url = "https://key:secret@hub.testingbot.com/wd/hub"
      capabilities = Selenium::WebDriver::Remote::Capabilities.new
      capabilities['platform'] = ENV['TB_PLATFORM']
      capabilities['browserName'] = ENV['TB_BROWSERNAME']
      capabilities['version'] = ENV['TB_VERSION']
      @driver = Selenium::WebDriver.for(:remote, :url => url, :desired_capabilities => capabilities)
    end

    def test_post
      @driver.navigate.to "http://www.google.com"
      element = @driver.find_element(:name, 'q')
      element.send_keys "TestingBot"
      element.submit
      assert_equal(@driver.title, "TestingBot - Google Search")
    end

    def teardown
      @driver.quit
    end
  end
  

Now we need to create a Rakefile which will start the tests in parallel.

require 'rubygems'
  require 'rake/testtask'
  require 'parallel'
  require 'json'

  @browsers = JSON.load(open('browsers.json'))
  @test_folder = "test/*_test.rb"
  @parallel_limit = ENV["nodes"] || 1
  @parallel_limit = @parallel_limit.to_i

  task :minitest do
    current_browser = ""
    begin
      Parallel.map(@browsers, :in_threads => @parallel_limit) do |browser|
        current_browser = browser
        puts "Running Browser : #{browser.inspect}"
        ENV['TB_BROWSERNAME'] = browser['browserName']
        ENV['TB_VERSION'] = browser['version']
        ENV['TB_PLATFORM'] = browser['platform']
        Dir.glob(@test_folder).each do |test_file|
          IO.popen("ruby #{test_file}") do |io|
            io.each do |line|
              puts line
            end
          end
        end
      end
    rescue SystemExit, Interrupt
      puts "User stopped script!"
      puts "Failed to run tests for #{current_browser.inspect}"
    end
  end

  task :default => [:minitest]

Queueing

Every plan we provide comes with a limit of concurrent VMs (how many tests you can run in parallel).
For example: if you have a plan with 5 concurrent VMs, it is possible to start more tests. TestingBot will queue the additional tests and run the tests as soon as slots become available.


One of the advantages in using our service is that you can run your tests in parallel.
You can run the same test across dozens of different browsers/versions at once, or run 20 tests at the same time on the same browsers. This drastically shortens your total test-build time.


Besides Minitest support we have documentation for RSpec, Test::Unit, Capybara and Cucumber testing:

Pick a Ruby test framework

  • Capybara

    Capybara is an integration testing tool for rack based web applications.

  • Cucumber

    Cucumber is a Ruby based test tool for BDD.

  • RSpec

    RSpec is a behavior-driven development (BDD) framework, inspired by JBehave.

  • Test::Unit

    Test-Unit is a xUnit family unit testing framework for Ruby.

  • Minitest

    Minimal (mostly drop-in) replacement for test-unit.

  • Watir

    Watir, pronounced water, is an open-source (BSD) family of Ruby libraries for automating web browsers.