TestingBot provides a cloud of browsers to run Automated, Live and Visual browser testing.
Sikuli is able to automate anything you see on your computer screen by using image recognition to identify components you want to interact with. This is very useful if you want to test things that are not easy to automate, for example native OS GUI components.
Since a lot of websites have upload functionality, it's important to know that this can be tested via Selenium.
Today TestingBot has added a new feature that should help you debug issues you encounter when running automated tests.
Suppose you're running a test and you notice something isn't quite working well (AJAX request is failing, Javascript errors, ...).
With Robot Framework you can build easy to read test cases, which can then be run via Selenium WebDriver on our Selenium Grid.
It allows using keyword driven, behaviour driven approaches and provides reports in HTML format.
This week we've been adding many more browser versions to our list of browsers you can pick from.
You can now instantly launch a Chrome browser as old as version 35 on our website and use it with your mouse and keyboard. Or use it in your Selenium IDE/Selenium Builder/Webdriver test to automatically test your website. We've added Chrome versions 35 - 45 for all Mac (Yosemite/Mavericks), Linux and Windows (XP, 7, 8, 10) platforms.
Windows 10 is now available on TestingBot to use during both manual and automated testing (Selenium WebDriver). This is the latest OS version available from Microsoft, with all installed updates, running the most recent version of Microsoft Edge.
With our TestingBot Tunnel you can easily and securely test your websites running on your local computer or internal network.
When you download and start the tunnel, the java process makes a call to TestingBot to create a new pristine VM which will act as a proxy between your network and our browser grid.
Today we've updated our TestLab, where you can upload your Selenium IDE tests and schedule test-runs, with 2 new features.
The first new feature is an optional custom error message. Before, TestingBot sent the error message received from Selenium to your e-mail or phone (SMS text message). Now, you can specify a custom error message for your alerts and use variables like %test_name% or %browser%, which will then be sent to your e-mail or phone.
