One of Ranorex’s greatest strengths is that non-coders can build rich test suites using very little code. This lowers the learning curve significantly and helps testers be productive regardless of their coding background. But little code does not mean no code at all. Most test suites need at least a little bit of code. These […]
Continue Reading...Category: Testing
Complexity is a Disease and Tests are a Symptom
Testing in software development is expensive. I’ve seen estimates ranging from 20% to 80%, some more reliable than others, none really truly reliable. And that’s the problem. Nobody knows how many or what kinds of tests to write, how much testing is too much or not enough, or how much tests should cost. In business […]
Continue Reading...Ranorex Speed #3: Optimizing RanoreXPaths
The key to optimizing RanoreXPath queries is to reduce the number of elements Ranorex has to evaluate as it scans the UI. This post shows a few ways to do that. A RanoreXPath, or RXPath for short, describes the path to an element or set of elements. As I explain in my post on RanoreXPath […]
Continue Reading...Ranorex Speed #2: The Repository Cache
Ranorex supports caching for app folders and rooted folders, which are two types of repository folders. The repository caching feature was designed specifically to improve test run performance. When an action associated with a repository item is executed during a test run, Ranorex tries to use the cache to avoid performing expensive and redundant searches. […]
Continue Reading...Ranorex Basics: RanoreXPaths and Repositories
In the previous post, we discussed plugins, elements and adapters, the most basic Ranorex components that make everything else tick. Whereas elements and adapters are the raw materials, RanoreXPaths and the repository are the sauce that makes it possible to query and work with the UI effectively. And while there isn’t much you can do to […]
Continue Reading...