Welcome to Novembers Product Update from the CrossBrowserTesting Team!
Making the Switch to Headless
As we mentioned in last months product update, we recently released Headless Testing to our feature portfolio. Developers and automated testers can now rapidly validate that their web application or website is working as expected, earlier in the development process and faster.
Initial feedback from customers utilizing our headless capabilities has been promising, just ask one that belongs to a large automotive group!
“Headless Testing allowed us to effortlessly switch all of our GUI tests to run in headless mode and reduce regression cycles from 6 hours to 2.25 hours.”
Also, check out a recent webinar the team presented to introduce Headless Testing!
Bitbar: Mobile App Testing
Can you believe its been 82 days since Bitbar joined the SmartBear family?? Us either, seems like it was yesterday!
Bitbar, the most flexible cloud-based mobile app testing solution allows you to use any framework to run manual or automated tests on thousands of real devices for your mobile app.
The CrossBrowserTesting and Bitbar team will be running a webinar to highlight how these complimentary tools can cover both your browser and mobile app testing. Register HERE!
Local Tunneling Improvements!
In addition to making our Local Connection tool more stable and reliable, we’ve also made it faster! Almost 6 times faster. The increase in speed is especially noticeable when running Screenshot tests or parallel Selenium tests to non-public websites. Make sure to download the latest version for your platform.
New Browsers and Operating Systems
Bug of the Month
We recently had an internal network issue at CrossBrowserTesting where failover to a redundant piece of hardware failed, causing a brief outage. This was caused by a configuration in hardware that, when failover was originally tested, worked fine. We eventually found the issue — after a period of time, the configuration for failover goes stale and stops working in a failover event. Testing immediately after setting up the device was not enough to catch this issue.
We thought this was interesting to share since there are a lot of variables, and it is hard to test for all permutations, or to even be aware of them. In this case, time since starting the service was just such a hidden variable.