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 = webdriver.Firefox()
driver = webdriver.Remote( command_executor='https://key:firstname.lastname@example.org/wd/hub', desired_capabilities=desired_caps)
To see how to do this, please select a combination of browser, version and platform in the drop-down menus below:
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 Lettuce Python test with our Tunnel:
1. Download our tunnel and start the tunnel:
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:
from lettuce import before, world from selenium import webdriver import lettuce_webdriver.webdriver @before.all def setup_browser(): desired_capabilities = webdriver.DesiredCapabilities.FIREFOX desired_capabilities['version'] = 'latest' desired_capabilities['platform'] = 'WINDOWS' desired_capabilities['name'] = 'Testing Selenium with Lettuce' world.browser = webdriver.Remote( desired_capabilities=desired_capabilities, command_executor="http://key:secret@localhost:4445/wd/hub" )
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 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.
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.
To run tests in parallel, we recommend using Nose and MultiProcessing, which makes it very easy to run multiple Python tests simultaneously:
pip install multiprocessing
Reporting Test Results
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 Python API client to report back test results.
tb = testingbotclient.TestingBotClient(key, secret) tb.tests.update_test(world.browser.session_id, status_message=.., passed=1|0, build=.., name=..)