
How Aggressively Should an Application Update Its Dependencies?
Should an application or service in production aim to keep its library dependencies as current as possible? Or, at the other extreme, update them only as a last resort?

Should an application or service in production aim to keep its library dependencies as current as possible? Or, at the other extreme, update them only as a last resort?

In the age of DevOps, one agile approach has become more relevant than ever: continuous testing. Here are four strategies that will help you strategically implement a scalable continuous testing process across the enterprise.

You wouldn’t drive a car by relying only on the speedometer and fuel gauge. So why would you run your software testing this way? Maybe it’s time to rethink the way that you’re using metrics.

Over the years, I’ve heard many, many software testers insist their management expected them to “automate everything.” In some ways it seems perfectly reasonable. But does this approach to test automation make sense? Can we do better?


Identify and correct problems sooner, rather than later: That’s the heart of the “shift left” slogan. But to do so with security — to cultivate not just DevOps, but DevSecOps — is one of application development’s thornier problems.
We are pleased to announce the general availability of Ranorex Studio 9.3.4, with support for iOS 14 and Android 11 mobile testing, plus QT 5.15.

We can validate whether a product is working as expected, but testing has to stop at some point so the product can be released. Here are six questions to help decide that it’s time to stop testing.

Reduce your test reporting and maintenance effort by integrating Jira with Ranorex Studio for test automation. Learn how in this recap of our recent live webinar.
