CrossBrowserTesting Reviews

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.

Our site's conversion from a static to an adaptive flexible layout was a major goal for our web site, and CrossBrowserTesting was an invaluable tool for trying out that new code. Cross-device testing was essential.

We could not have been certain that we would have achieved our goal without it.

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.

We would not be able to provide our services without their tools. Their tools, or ones like it, are absolutely essential for us to provide high quality and continuous integration for our services.

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

CrossBrowserTesting improved my organization because it eliminates the need for a physical device with a tester to cover our used browsers. This saves the company money and time.

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.

This solution improves the customer experience using Quartzy. 

It has saved us time and money on our web app. It would taken time to look across many devices and browser versions every time that we made changes to the front-end of the application. It also means less "broken pages" are seen by users by the time a feature is ready to launch.

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. 

CrossBrowserTesting is an essential tool in our organization for key projects. Our marketing team gains the most from utilizing this tool to be able to test ongoing web enhancements and different tracking measures.

It crucial for our marketing team to be able to check our web pages against various devices and browsers with cleared caching to be able to get a viable user-end experience and accurate reporting. With the live testing tool and screenshots, we are able to compare the different results observed with the devices and browsers and implement fixes.

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.

We've seen an improvement in functionality across browsers. We're able to find where alignment is off or functionality is failing due to some "feature" with a specific browser. Being able to find issues before the customer does is key.

The snapshots of what the site looks like at any given time give us insight into where our UX is off. Similarly, if we are having issues with the functionality then we can catch them even if our QA team missed them.

Having it all in one place makes finding and fixes issues so much quicker.

We use CrossBrowserTesting for testing our web-based applications.

We had some issues with the onboarding process and the cloud conductivity could improve.

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.

This solution helps lower the overhead cost associated with buying multiple devices. It saves time because we are not constantly upgrading to the latest OS on each device.