I've been using Ranorex for web automation testing purposes for 3+ years now, and I can say it's the best UI automation tool I've used so far.
The application under test is a fairly huge site, where the end users can create individual accounts, but also enterprise ones that, depending on the account type, have a LOT of options that can be tweaked, configured and administered in a lot of different ways.
Besides the main web app, there are interactions with two 3rd party billing platforms and CRM product.
Organizing tests seems pretty easy and straightforward to me, since you can create in your test suite countless folders and test cases. You can think at it like a file and folder structures where your folders are, well, folders in the test suite and the files, test cases. You can go as deep with the structure as you like.
Besides that, you can also group test cases in something called test configs (e.g. a test config may contain one or more test cases).
In my case, we have
.txt files containing multiple test configs, and use
Jenkins to feed one test config to a virtual machine that starts executing all the test cases belonging to it.
Now, for data driven testing, you can have something that they call Simple Data Table that is nothing else other than a table provided by the tool. Other options are using CSV files, Excel files (I'm using
.xlsb, especially for large data files. Read more here and here about why is better to use
.xlsb) and SQL tables, although I didn't used it myself.
Note: For performance improvements for the test suite GUI, you may want to disable the auto-loading of the data (in case you have a fair amount of data-driven test cases). It's the checkbox from the image here.