CrossBrowserTesting Pros and Cons

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.

When developing new pages that have questionable functionality or coding, we will often use CBT to test it in a browser. CBT works with our testing environment and development site.

I can run a page through the screenshot tool, then send a URL with the results to my team.

CrossBrowserTesting allows us to test our site with real-world devices in real-world scenarios and find what we're missing.

This solution helps lower the overhead cost associated with buying multiple devices.

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.

Being able to test on real devices via the virtual connection is wonderful, but it can cause some lag and load time issues while testing.

The screenshot tool defaults to a screen layout instead of a full page test. I find it a bit cumbersome that I can't have it run a full screenshot as my default.

This solution would benefit from faster testing and support for more devices.

I have had quite a few issues trying to use a virtual machine to test our application on.

It would be useful if we can run the live-testing test cases on multiple platforms at the same time, instead of waiting for one session to finish.