Today we’re happy to announce the launch of a new feature: live manual testing.

With this new feature you can interact with any browser in our cloud, straight from inside your own browser.
Once you click a browser and operating system in our new Manual Testing Member Area, we’ll spin up a new Virtual Machine and launch the browser you picked in less than 30 seconds.

You’ll be able to control the Virtual Machine from inside your browser, take screenshots, change the screen resolution and collaborate live with other co-workers.
Since TestingBot runs on two datacenters: one in the US and one in Europe, we provide the fastest experience with a minimum of latency.

When you start a tunnel on your computer, you’ll be able to manually test your internal websites from inside our cloud.

Ready to get started? Head on over to our feature page or immediately start testing!

We’re excited to announce that starting from today, our customers can choose to either run their tests on our existing US cloud or on our new European based cloud!

With this new datacenter in Europe (Ireland), we’ll provide faster test times for our customers residing in Europe.
A quick comparison on the difference in latency when residing in Europe:

For testers residing in Europe, using our European cloud will mean a decrease in latency of over 50%!

The service and features we provide are identical across both clouds. When running a test in Europe, your request will only go through European servers to guarantee maximum speed.
Our Tunnel has been updated to provide a “region” option, which means you can choose to run your local tests through a European or US based pristine tunnel.

To get started, all you need to do is use our European Selenium Grid, which runs on: europe.testingbot.com on ports 4444 and 80.
More information and examples are available on our Europe page.

You can now specify a custom screen resolution when running any Selenium test on our grid.
TestingBot can now modify the screen-resolution on Windows, Linux and Mac!

These are the available screen resolutions:

• 800×600
• 1024×768
• 1280×960
• 1280×1024
• 1600×1200
• 1920×1200
• 2560×1440

You can find info and more test options on our support options page.
The same screen resolution settings are available in our TestLab as well.

Enjoy!

With Appium on TestingBot you can now run WebDriver tests against hybrid and native iOS apps.
There’s no need to do anything special to your iOS app, just supply an URL to the zipped version of the .app file in the desired capabilities and Appium will extract your app and run tests against it in an iOS Simulator.

Since Appium uses the WebDriver protocol, you are free to choose any programming language you want to run tests against it: PHP, Ruby, Java, .NET, NodeJS, Python, …
Because Appium uses Apple’s UIAutomation, there’s no need to recompile or modify your app to run tests against it.

Starting from today, all our customers can run Appium WebDriver tests against iPhone/iPad simulators in our cloud. Run iOS tests in parallel without having to worry about setup or maintenance.

You can find more info and an example video of an Appium test on our Appium page.

Below is a guide to run your Selenium tests with Travis CI.
We offer TestingBot status badges to indicate your Selenium tests status on your GitHub pages.

Set up Travis CI

Sign up at Travis CI and connect your GitHub project with Travis CI.
You can find information on how to do this at the Travis CI help section.

Sample Selenium Test

Add a simple Selenium test to your GitHub project, modify the .travis.yml file in your repository to indicate you want to run a Selenium test.

language: node_js
node_js:
  - 0.8
env:
- [
    {secure: "akuE0dld1Ke9mahjUUrQhUZRYWasdfewfwefewfZlbvOx\nqaPybirPGsDmImvcktaAkjLxpePd0V1+ak+4dws7dTrFfEsdvsdsdvsdvds2\nud1q5oGOzEqfiRGxY/fJHLWlaQ609Bsdfdsfds2VeY1Z/V7N9iQ="},
    {secure: "JGfkAfr/SOlzV+NpgNi3fxP4F2usdfdsveGAppugHj1IxhoyjY\nOp07x4p1hdIfWVF03RqUrPNXkl72+yh53pv2fUzsdfsd3434GRjGy6J6\notuA/N+xs0+TP2ENlCmDauwO32Okfojvj7CgvsdfdsfRyaFzIGWPdw="}
  ]
script:
- "node tests/examples/*.js"

The two secure lines in the above example are your TestingBot key and secret, which are used to run a test on our TestingBot Selenium Grid.
To generate these 2 lines, you need to install the Travis CI gem and run these commands with your own key and secret:

travis encrypt username/projectname TESTINGBOT_KEY=key
travis encrypt username/projectname TESTINGBOT_SECRET=secret

Now you can use the encrypted TESTINGBOT_KEY and TESTINGBOT_SECRET environment variables in your tests.
Remember to indicate your test’s privacy setting as “public” (privacy = true) if you want to use the test status badges we provide.

Here’s an example in NodeJS:

var webdriverjs = require('tbwdjs');
var client = webdriverjs.remote({
    host: 'hub.testingbot.com',
    desiredCapabilities: {
        browserName: 'internet explorer',
        version: 9,
        platform: 'WINDOWS',
        api_key: process.env.TESTINGBOT_KEY,
        api_secret: process.env.TESTINGBOT_SECRET,
        name: (process.env.TRAVIS_JOB_ID ? ("Travis Build " + process.env.TRAVIS_JOB_ID) : "Simple Test"),
        privacy: true
    }
});

client
    .testMode()
    .init()
    .url('http://google.com/')
    .titleEquals('Google')
    .end();

Get your TestingBot badge

Once your first Selenium test has ran via Travis, you can start displaying its status with our Status Badges:

<a href="http://testingbot.com/u/key">
  <img src="http://testingbot.com/buildstatus/key" alt="Selenium Test Status">
</a>

More information

Our help page regarding Travis CI integration has more info: Travis CI + TestingBot

Today we have added PhantomJS to our Linux VMs on our Selenium Grid.
You can now run your WebDriver tests on PhantomJS + Ubuntu.

PhantomJS is a headless WebKit solution which is very fast, it does not suffer from slow browser startup times or other issues you might encounter with browsers.
Together with Ivan De Marino’s GhostDriver, we can now run Selenium WebDriver tests with PhantomJS.

An example of how to run a simple test with Ruby and PhantomJS on our grid:

caps = {
  :browserName => "phantomjs",
  :platform => "LINUX"
}

urlhub = "http://key:secret@hub.testingbot.com:4444/wd/hub"

client = Selenium::WebDriver::Remote::Http::Default.new
client.timeout = 120

@webdriver = Selenium::WebDriver.for :remote, :url => urlhub, :desired_capabilities => caps, :http_client => client
@webdriver.navigate.to "http://www.google.com/"
puts @webdriver.title
@webdriver.save_screenshot("./screenshot.png")
@webdriver.quit

The example above will open the homepage of Google, print the title of the homepage and save a screenshot of the page on your harddisk.

As PhantomJS and GhostDriver will be improved and updated in the future, we will keep on updating these on our Linux VMs.

Together with Ubuntu, PhantomJS is very fast:

PhantomJS + GhostDriver Ubuntu on our grid:
real 0m11.395s
user 0m2.588s
sys 0m0.225s

Google Chrome Ubuntu on our grid:
real 0m24.249s
user 0m2.476s
sys 0m0.128s

If you have any questions or suggestions for new features, please let us know.

Today we have added Windows 2012 (= Windows 8) VMs to our grid.
You can now run Firefox/Chrome and IE10 tests on Windows 2012 VMs.

To run a test on a Windows 2012 VM, you need to use WIN8 as the platform desired capability, see the following example:

caps = {
  :browserName => "internet explorer",
  :version => "10",
  :screenshot => true,
  :platform => "WIN8"
}

urlhub = "http://key:secret@hub.testingbot.com:4444/wd/hub"
client = Selenium::WebDriver::Remote::Http::Default.new
client.timeout = 120
@webdriver = Selenium::WebDriver.for :remote, :url => urlhub, :desired_capabilities => caps, :http_client => client
@webdriver.navigate.to "http://testingbot.com/"
puts @webdriver.title
@webdriver.quit

The full list of all browser combinations we support: 91 browser combinations

We’ve also updated the Selenium version on all VMs has been updated from 2.25.0 to 2.26.0 (most recent version), together with the most recent IEDriver and ChromeDriver versions.

Happy testing!

Today we have added IE10 to our Selenium grid.
You can now run WebDriver and Selenium RC tests against Microsoft’s latest Internet Explorer browser: IE10.

Give it a try with your WebDriver test:

DesiredCapabilities caps = DesiredCapabilities.internetExplorer();
caps.setCapability("platform", "Windows");
caps.setCapability("version", "10");

You can see a list of all browsers (65 combinations!) we support at our browser page.

OperaDriver has recently been updated to support running Selenium tests on the Opera Mobile Emulator.
The update will land in Selenium 2.26, but we couldn’t wait and decided to already add it to our Selenium Grid.

By specifying some desired capabilities, you can run your tests on a specific emulated device.
You can change the resolution of the screen, the pixel density and the UI.
Here’s an example where we run a test on the tablet UI with a 800×600 display:

caps = {
  :browserName => "operea",
  :platform => "LINUX",
  'opera.product' => 'mobile',
  'opera.arguments => '-tabletui -displaysize 860x600'
}

urlhub = "http://key:secret@hub.testingbot.com:4444/wd/hub"
client = Selenium::WebDriver::Remote::Http::Default.new
client.timeout = 120
@webdriver = Selenium::WebDriver.for :remote,:url => urlhub , :desired_capabilities => caps,:http_client => client
@webdriver.navigate.to "http://testingbot.com"
puts @webdriver.title
@webdriver.quit

Right now Opera Mobile support is still robust and in need for some (minor) tweaks, but we think it’s starting to look good.
If you want to give it a try, you can run the example on our grid.

Interested in running tests on other mobile devices? Check out our supported emulators (iPhone/iPad/Android) on our mobile page.

More information about OperaDriver and its emulator is available on: [dev.opera.com] Introducing mobile browser automation and [github.com] OperaDriver

Currently we are the only company providing OS X support to our customers.
When you run a test on one of our Mac nodes, we reserve a dedicated VM running OS X Lion on a beefy Mac Pro running VMWare.

These last few weeks, we’ve made quite a few optimizations on OS X to improve overall testing, here’s what we’ve done:

Added OS X Safari 6 with WebDriver

This week we’ve added Safari 6 Mac OS X to our list of supported browsers.
With 58 browser/OS combinations, we’ve got most of the combinations covered.

Next to Safari 6, we also provide Safari 5 on Mac OS X Lion and Windows.
Yesterday we have added support for our Tunnel to Safari WebDriver, which means you can now run tests against Safari 5 and Safari 6 from your local network.
Our Tunnel is now supported with all browser combinations, even with iPhone/iPad and Android emulators.

Improved iOS Testing

We’ve learned from extensive testing with the iOS simulator that the simulator sometimes acts strangely.
After a lot of debugging and fixing, we’ve come at a point where we think running tests on iOS is finally stable.

More browser combinations

You can now run tests with Firefox 3-14, Chrome, Opera and Safari 5+6 on a Lion instance.

Future optimisations

We’ll be upgrading our nodes to OS X Mountain Lion and add better Opera support in the next few weeks.