Our team uses the live testing feature almost daily to check for differences within a web page from browser to browser. The live testing feature is also useful when submitting data from our web pages using different parameters that affect cookies and session storage.

Each new session started with the live testing feature allows for a cleared browser and new experience to be able to not only see these attributes on the page clearly but also pass clean data.

The screenshots tool is another feature that we are able to utilize to get a quick grasp of high-level layout differences that may present during testing. 

Static screenshots are the feature most often used, because they are a simple method of detecting problems. I can run a page through the screenshot tool, then send a URL with the results to my team. Though it is probably a minor part of what CBT does, I find it the most useful.

Being able to test across actual devices is key. Without seeing how your site really works against an older device and/or browser, you can't truly know if your customers will have a good, poor, or bad experience.

Device emulators within a browser can only do so much and at the end of the day, they really are rendering with their engine, not the actual engine the customer is using.

CrossBrowserTesting allows us to test our site with real-world devices in real-world scenarios and find what we're missing. Better you find out the issues before your customer does.

We have saved the cost to buy in house devices.

Real device sessions instead of simulators

Screenshot test across the web and mobile devices at once which returns images

Shareable reports

Selection of the required device, Platform, and browsers.

Record and Replay is the most used functionality for us, as we can record the test cases and play them on multiple combinations of platforms.

Live testing with the previous history of test cases is a useful feature.

Screenshot testing is a useful feature for applying the same test case on multiple browsers.

The most valuable feature is that it gives us "real" OS devices that are available to test. On top of that, we don't have to ensure that all of the devices are up to date. 

The local connection is pretty awesome at the moment of testing the developments created at home, and the tool getting the proof of your testing is awesome (videos and screenshots).

I am frequently using live testing to verify the UI in different devices and IE browser. Also, I've started using a screenshot, but it is not very useful for me, since the page does not load properly without loading another CSS file.

• Live browser testing: Testing customer issues.
• Selenium access: Automated testing of the administrative interface, as well as automatic testing for new JavaScript releases of our tracking snippet.
• The screen shot portal is essential for an easy way to run tests across hundreds of browsers and retrieve screenshots which then indicate success or failure.

The ability to choose from many devices is the best feature. It also supports browsers and offers version selection to cover what we need.

I use the screenshot functionality most frequently and live testing on occasion. I have also used the record and replay functionality once or twice.

With screenshots, I can quickly verify a page looks good universally in minutes. It is also shareable to all my coworkers, so reporting issues to engineering are simple.

The possibility of having a real-time web service with a large number of real devices with different operating systems and browser versions is a great advantage for us. 

Other features from CrossBrowserTesting, like screenshots or screen recordings, are a nice plus in the service.

At the moment, all our deploys depend on results of automation. If the tests are failing, then we know that something is wrong at the early stages of development. Live testing helps us to debug problems across all browsers.

What sets CrossBrowserTesting apart from the rest is their ability to quickly respond to the needs of their customers. Every time I contacted support with a feature that I really needed, they were able to enhance their offerings to accommodate me. For example, I needed the ability to initiate a session with updated TLS settings (regardless of the browser/OS default settings) so I could run automated tests in legacy browsers. In less than two weeks, the team had added this enhancement for me. 

Another great thing about CrossBrowserTesting is I can quickly access sessions and interact with the browser with virtually no lag time. CrossBrowserTesting recently introduced a WebRTC option which speeds up the experience even further. With other cloud testing tools, I have experienced lag times and inconsistencies (in regard to spinning up a new session). I have very rarely had issues with CrossBrowserTesting in this regard. If there are any issues, the support team responds immediately. There are always honest and forthcoming about what caused the problem and how they are fixing it.

• Cross browser testing
• Live test
• Video recording of the script running in a cloud server.

• Selenium Grid allows testing multiple platforms to insure functionality for most users.
• The ability to replay sessions is valuable for tracking down issues.

The features that I find most useful and the ones that I use the most are local site testing, device and browser testing, and screenshots.

I am a big fan of the clean, uncluttered layout of the site on landing as well as the aids given to you when testing mobile products, especially the keyboard posting tools which negate tapping out my individual data entries. The extensive range of products available to simulate is also something I have come to appreciate as it has resulted in an ability to broaden the scope of our tests (something no FT tester should sneer at).