Skip to main content

Selenium Browser Testing with TestingBot

TestingBot is an online service which provides a Selenium Grid in the cloud. By utilizing TestingBot, you have immediate access to over 600 browser and device combinations to run both Automated Selenium and Manual tests. Ranging from IE6 to Chrome dev builds, from Windows XP to Windows 10 and macOS Sierra.

Instead of setting up and maintaining your own Selenium Grid with all possible browser combinations, you can rely on TestingBot to provide you with an extensive Selenium grid of both older and new browser versions. Because of this large Selenium Grid, you can easily run multiple tests simultaneously. For example; you can run the same test simultaneously on 40 different browser combinations, or run 40 different tests all on the same browser at once. This means your total test duration shortens dramatically, giving you early test feedback.
Running Appium tests is also possible. TestingBot provides iOS Simulators and Android emulators to run your Appium tests. In the coming months, TestingBot will be providing Automated and Manual real mobile device testing as well.

If you are looking to run tests against a website you're still developing on your computer or local network, you can use the TestingBot Tunnel. This allows you to run Automated and Manual tests on websites that are not yet available to the public.

If you're still using Selenium IDE or RC, you can upload your tests and test suites to TestingBot. Then you can schedule when the tests need to run and on which browsers. After each test run, you will receive a report and you can set up alerting to be notified when a test fails.

With the Automated test examples, ranging from PHP, Ruby and Python to Java, C# and NodeJS you can immediately start running your automated WebDriver tests.
And with the Manual testing, you can take control over any browser straight from your own browser, no setup required. Change the screen resolution, take screenshots and share with colleagues.

Interested? Start your free trial and run your browser tests in the cloud!

Popular posts from this blog

How can you save resources when instantiaing driver?

I asked on my previous post about what was wrong in instantiating driver on set up method? And here is the solution video on my YouTube channel (After 5 years of gap I finally added new video tutorial :)) The solution described on video tutorial uses following set up - public class BaseClassOnDemandDriverSetup { private WebDriver driver ; @BeforeMethod public void setupTest () { // Any other set up goes here } @AfterMethod public void teardown () { if ( driver != null ) { driver .quit() ; } } public WebDriver getDriver () { if ( driver == null ) { WebDriverManager. chromedriver ().setup() ; driver = new ChromeDriver() ; } return driver ; } }

Using chrome console to test xPath and css selectors

Since the advent of selenium there have been many plugin to test xPath / css selectors but you don’t need any of them if you have chrome browser. Using Chrome console you can test both xPath and css selectors. Launch website to be tested in chrome browser and hit F-12 and you would see chrome console opened in lower pane of application - Hit escape key and console would open another pane to write element locators - And now you can start writing xPath or css selectors in chrome console and test them - The syntax for writing css id - $$(“ ”) And hit the enter key. If your expression is right then html snippet of the application element corresponding to the css selector would be displayed - If you mouse over the html snippet in chrome console then it would highlight the corresponding element in application - If you want to clean console of previously written element selectors then just hit ctrl+L keys and chrome console would be empty again. Pro

Using xPath to reach parent of an element

Well, I am big fan of css locator my self there are times when css locators don't fit requirement. One such requirement is when you want to navigate to parent element of an element and may be parent of parent and even more. Unfortunately css locators don't provide any mechanism to navigate to parent of an element. See this for more. Of late I came across a scenario when I wanted to click on a link depending upon the text in a text box. Herein parent of text box and parent of link were at the same location. More over there could have been many such combinations in application. Fortunately I just need to pick first such instance and Web Driver any way considers only first instance when multiple locators are found matching an element. Element in question is in following html - Here I need to click on highlighted anchor on the basis of input element (which is also highlighted in image) Herein first I need to reach div parent (class = 'left couponmainarea