When developing new pages that have questionable functionality or coding, we will often use CBT to test it in a variety of browsers and devices. CBT works with our testing environment and development site.  Our greatest concern is universal appearance and functionality, thus we test a great many browsers.

Primary use case is to run an online analytics company which requires JavaScript compatibility across all browsers. We use this tool to test and deploy release updates whenever changes are made. Also, they have a Selenium portal which is useful for doing browser testing for our administrative interface and automated user testing. Finally, they have the ability to launch live browser environments. This is invaluable in diagnosing customer issues and replicating problems within specific browsers.

A wide variety of browser testing for most of my company's internal and frequently used websites.

We needed a consistent way to test our site against multiple browsers and devices. By having access to different devices sporting different versions of each OS, we can ensure our customers are going to be getting a satisfactory experience. Without this, we are guessing as to how or what experience our users are getting.

It's also helpful in researching issues that our customers report when we know what devices/OS/browser they're using. Using a browser emulator doesn't cut it and having a live device browser to interact with the site is invaluable.

The primary use case we use this solution for would be to test our Marketing websites.

With our websites, the users' needs are always expanding and growing. There are many times we are adding and taking away content, as well as modifying existing content and page layouts. Different campaigns are created with tracking measures and parameters that are validated for company use and reporting.

It is important in these cases that we are able to run tests on different devices and browsers with clear cookies and session storage to be able to see any differences and provide clear accurate results. 

Where I work as a QA analyst, we have developed a web app to help life scientists organize their labs and order lab supplies from a variety of manufacturers at low prices. 

My primary use case of CrossBrowserTesting is to ensure new features that we have launched, or are about to launch, look correct and work as expected on all the most common browsers across the most common OSs.

We use CrossBrowserTesting for testing our web-based applications.

Our primary use case is testing our application on various tablet/mobile devices. It is nice to have all of the devices you need in one place.

Manual and automated (Selenium) continuous testing of development and production websites to protect against broken code deployments.

We primarily use CrossBrowserTesting to troubleshoot front-end issues in various browsers and devices.

We work in the web design/development sector. It is really important for us to bring the total warranty of sites to 100% mobile responsive. It is really difficult, but with CrossBrowserTesting, we can do all the testing that we need to do with it.

Our primary use cases for this solution are:

• Feature validation of our product on multiple OS/mobile/browser combinations
• To expose platform-specific issues early in the testing life cycle
• To find usability issues and differences between desktop versus mobile versus tablets

I used CrossBrowserTesting for testing on different browsers on desktop and phone environments with different browser versions for our sites.

I use CrossBrowserTesting to run Selenium tests in the cloud. I have created a custom QA automation tool for my company and integrated it with CrossBrowserTesting via the Selenium API. I send the commands to CrossBrowserTesting over the API and my tests get executed in the desired browsers/OS combinations. I also use the CrossBrowserTesting Selenium API to retrieve a full list of all browser/OS combos so my QA automation interface can allow users to choose what browsers they want to test.

In addition, our entire front-end team uses the CrossBrowserTesting live testing feature to investigate browser issues and do manual QA testing.

My primary use for this product revolves around simulating various mobile and tablet responses to company web apps on an internal FT environment.

Use of CBT to test the UI in different mobile devices since the experience is different with a real device vs. resizing window browser. Also, it's very useful to test the UI in Internet Explorer.

We have a bunch of JavaScript libraries which are used on thousands of websites for showing advertisements. 

When I had just joined the company, there were no tests at all and the deploying process was very unpredictable. Therefore, we decided to cover the libraries by unit and integration tests.

We are using this feature to run our application in all the updated browsers popularly used.       

We develop web and mobile applications and need to test our applications across different browsers and different devices across all operating systems.