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 'selenium-webdriver'
require 'test/unit'
class SampleTest < Test::Unit::TestCase
def setup
options = Selenium::WebDriver::Chrome::Options.new
options.add_option('platformName', 'WIN11')
options.add_option('browserVersion', 'latest')
options.add_option('tb:options', {
'key' => 'API_KEY',
'secret' => 'API_SECRET',
'name' => 'Test::Unit Example'
})
@driver = Selenium::WebDriver.for(
:remote,
url: 'https://hub.testingbot.com/wd/hub',
options: options
)
end
def test_google_search
@driver.navigate.to 'https://www.google.com/ncr'
element = @driver.find_element(:name, 'q')
element.send_keys 'TestingBot'
element.submit
assert_equal('TestingBot - Google Search', @driver.title)
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 :chrome
options = Selenium::WebDriver::Chrome::Options.new
options.add_option('platformName', 'WIN11')
options.add_option('browserVersion', 'latest')
options.add_option('tb:options', {
'key' => 'API_KEY',
'secret' => 'API_SECRET'
})
driver = Selenium::WebDriver.for(:remote, url: 'https://hub.testingbot.com/wd/hub', options: options)
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.
options = Selenium::WebDriver::Chrome::Options.new
options.add_option('platformName', 'WIN11')
options.add_option('browserVersion', 'latest')
options.add_option('tb:options', {
'key' => 'API_KEY',
'secret' => 'API_SECRET'
})
driver = Selenium::WebDriver.for(:remote, url: 'https://hub.testingbot.com/wd/hub', options: options)
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 'selenium-webdriver'
require 'test/unit'
class SampleTest < Test::Unit::TestCase
def setup
options = Selenium::WebDriver::Chrome::Options.new
options.add_option('platformName', 'WIN11')
options.add_option('browserVersion', 'latest')
options.add_option('tb:options', {
'key' => 'API_KEY',
'secret' => 'API_SECRET',
'name' => 'Tunnel Test'
})
# Point to the tunnel running on localhost:4445
@driver = Selenium::WebDriver.for(
:remote,
url: 'http://localhost:4445/wd/hub',
options: options
)
end
def test_internal_site
@driver.navigate.to 'http://localhost:3000' # Your internal website
element = @driver.find_element(:css, 'h1')
assert(element.text.include?('Welcome'))
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_chrome.rb and test_firefox.rb
require 'selenium-webdriver'
require 'test/unit'
class ChromeTest < Test::Unit::TestCase
def setup
options = Selenium::WebDriver::Chrome::Options.new
options.add_option('platformName', 'WIN11')
options.add_option('browserVersion', 'latest')
options.add_option('tb:options', {
'key' => ENV['TB_KEY'],
'secret' => ENV['TB_SECRET'],
'name' => 'Parallel Chrome Test'
})
@driver = Selenium::WebDriver.for(
:remote,
url: 'https://hub.testingbot.com/wd/hub',
options: options
)
end
def test_google_search
@driver.navigate.to 'https://www.google.com'
element = @driver.find_element(:name, 'q')
element.send_keys 'TestingBot'
element.submit
assert_equal('TestingBot - Google Search', @driver.title)
end
def teardown
@driver.quit
end
end
require 'selenium-webdriver'
require 'test/unit'
class FirefoxTest < Test::Unit::TestCase
def setup
options = Selenium::WebDriver::Firefox::Options.new
options.add_option('platformName', 'WIN11')
options.add_option('browserVersion', 'latest')
options.add_option('tb:options', {
'key' => ENV['TB_KEY'],
'secret' => ENV['TB_SECRET'],
'name' => 'Parallel Firefox Test'
})
@driver = Selenium::WebDriver.for(
:remote,
url: 'https://hub.testingbot.com/wd/hub',
options: options
)
end
def test_google_search
@driver.navigate.to 'https://www.google.com'
element = @driver.find_element(:name, 'q')
element.send_keys 'TestingBot'
element.submit
assert_equal('TestingBot - Google Search', @driver.title)
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="API_KEY" TB_SECRET="API_SECRET" parallel_test -n 2 test_chrome.rb test_firefox.rb
Queuing
Every plan we provide comes with a limit of parallel tests.
If you exceed the number of parallel tests assigned to your account, TestingBot will queue the additional tests (for up to 6 minutes) and run the tests as soon as slots become available.
Mark tests as passed/failed
As TestingBot has no way to determine 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('API_KEY', 'API_SECRET')
api.update_test(@driver.session_id, { name: 'My Test', 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.
-
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.