Features

Test::Unit Automated Testing

See our TestUnit example repository for a simple example on how to run TestUnit tests in parallel on TestingBot.


Example Test::Unit

require 'rubygems'
require 'selenium-webdriver'
require 'test/unit'

class SampleTest < Test::Unit::TestCase
	def setup
		url = "https://API_KEY:API_SECRET@hub.testingbot.com/wd/hub"
		@driver = Selenium::WebDriver.for(:remote, :url => url)
	end

	def test_post
		@driver.navigate.to "http://www.google.com/ncr"
		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

Before:
driver = Selenium::WebDriver.for :chrome

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

Specify Browsers & Devices

To let TestingBot know on which browser/platform/device 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.



Testing Internal 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 Ruby WebDriver test 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 securely through the tunnel to TestingBot and back:


require 'rubygems'
require 'selenium-webdriver'
require 'test/unit'

class SampleTest < Test::Unit::TestCase
	def setup
		url = "http://API_KEY:API_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

Run tests in Parallel

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.


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


First, you need to add the parallel testing gem to your Gemfile.
This Gem will allow you to run multiple tests simultaneously.


Create 2 test files: test_google_ie9.rb and test_google_ff.rb


test_google_ie9.rb
require 'rubygems'
require 'selenium-webdriver'
require 'test/unit'
 
class SampleTest1 < Test::Unit::TestCase
	def setup
		key=ENV['TB_KEY']
		secret=ENV['TB_SECRET']
		url = "https://#{key}:#{secret}@hub.testingbot.com/wd/hub"
		capabilities = Selenium::WebDriver::Remote::Capabilities.chrome
		capabilities.platform = :WINDOWS
		capabilities.browserName = "internet explorer"
		capabilities.version = 9
		@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

test_google_ff.rb:
require 'rubygems'
require 'selenium-webdriver'
require 'test/unit'
 
class SampleTest1 < Test::Unit::TestCase
	def setup
		key=ENV['TB_KEY']
		secret=ENV['TB_SECRET']
		url = "https://#{key}:#{secret}@hub.testingbot.com/wd/hub"
		capabilities = Selenium::WebDriver::Remote::Capabilities.chrome
		capabilities.platform = :WINDOWS
		capabilities.browserName = "firefox"
		capabilities.version = "latest"
		@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 you need to instruct the parallel_test gem to run these two tests in parallel:

TB_KEY="key" TB_SECRET="secret" parallel_test -n 2 test_google_ie9.rb test_google_ff.rb

Queuing

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.

Mark tests as passed/failed

As TestingBot has no way to dermine whether your test passed or failed (it is determined by your business logic), we offer a way to send the test status back to TestingBot. This is useful if you want to see if a test succeeded or failed from the TestingBot member area.


You can use our Ruby API client to report back test results.

api = TestingBot::Api.new(key, secret)
api.update_test(driver.session_id, { :name => new_name, :success => true })

Other Ruby Framework examples

  • 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.