Since Ranorex 6.0 it's possible to do Remote Tests with Ranorex Agents. Starting of such tests is only possible with Ranorex Studio. It would be great to start these tests via CommandLine.

It would be great if I could convert my report to PDF, and easily send it via email.
Now I have to post-process the report to create PDF, and configure a custom mail logger to send it via email. That is possible for me, but not every tester in my team without coding experience.
For future projects, it would be awesome if this functionality would be easily available to everyone.

(submitted via email and analogously translated to match the purpose of this platform)

It will be great to create an UI IF sequence insteado of creating a method to do this kind of things. This controls could start with very easy stuff like take an action if a popup ocurs or not.

I would like to see a full dark theme for studio, that changes windows, title bars, menus, buttons, project view, module browser, test suite view, properties, and any other elements of Ranorex Studio to a dark theme with white or syntax colorized text. Not just the code editor, but all of Ranorex Studio should be able to be set to "dark theme". I use the dark theme for Visual Studio, and would like the same for Ranorex Studio.

Our tests have to deal with a lot of unexpected popups occurring during test (e.g. windows update).
Unfortunately creating these popup watchers and make them work is so advanced that not everyone in the team can do it. Even worse, you have to use code most of the testers do not like (not to say “are afraid of”).
A UI would be perfect that allows everyone in the team to make the test stable against popups. Advanced topics can still be handled in code. Thank you.

(submitted via email and analogously translated to match the purpose of this platform)

it would be nice to have a better way to upgrade solutions with new Ranorex versions than opening them one by one for upgrade.

To prevent ugly merges involving rxtst files, we would like to isolate the tests being worked on by different team members to unique test suites (rxtst files). The problem is that only the main Test Suite gets an executable file and only it can be run and deployed on remote machines. We would like Ranorex to support multiple Test Suites in a single project (maybe each rxtst gets an exe generated so they can be called via command line).

I see another user had the same request here: https://www.ranorex.com/forum/adding-multiple-rxtst-files-to-project-improving-svn-t9742.html

Currently, the popup watcher runs in a separate thread, which does not allow interaction with test running in the main thread. Possibility to pause/stop main thread from popup watcher would be really handy! For example, in case the popup watcher finds an element, which should never appear during the test, it would be really great to have the possibility to stop the test and set it as failure. There is plenty of posts at forum regarding this issue. Thanks.

In the current Ranorex Studio, the embedded Spy and Recorder point to Spy 32bit and Recorder 32bit.

For automating tests for a 64bit app, the 64bit Spy and Recorder are needed (delivered as separate tools).

It would be pretty useful to have some configuration settings to choose the Spy&Recorder version Ranorex Studio will use/trigger: 32bit vs 64bit.
This way one would keep the benefit (more productive) of working only with/from within Ranorex Studio.

Hopefully this would get in the next Ranorex Studio releases.

Thanks a lot,
Cheers.

P.S. Congrats for the "Uservoice" btw. Great idea ;)

We want to start a Windows-Jenkins-Slave to start a Ranorex-Test in a Jenkins-pipeline. This scenario is only usefull if Ranorex could read Excell files without Microsoft Office installed (licensecost)

It would be nice to have the ablity to use the same language features as in visual studio. Without having to worry about version difference.

The ability to start a test run and walk away. Then have the option on only pass, only fail, or both so that you are notified that your SUT needs attention. Particularity useful for long weekend runs where you could quickly log in to restart a failed test if needed if you had only known. The email should contain the standard report in html and/or pdf as well as an option for a screenshot of the desktop for a quick glance at what went wrong.

Unfortunately there is currently no object identification for shadow DOMs.
This prevents using ranorex with certain web apps that utilize web components and shadow DOMs specifically.

No workaround.

Currently, in order to perform drag and drop action, we need to use Mouse.MoveTo()
Mouse.ButtonDown()
instead of writing two lines of code, it would be nice if there is a drag and drop action in one line.
E.g.:
DragAnDrop(element 1, element 2)

It would be helpfull if it would be possible to run the remote agent client without admin rights because in larger corporations it is difficult to get a user with these rights.

We are testing a software in a browser that sometimes need time to load data. When loading a message is shown. The problem is that the tag is always there only the visible status changes. So it would be great to have a funktion like 'wait for not exist' also for 'wait for not visible'.

When scheduled an execution, we can't see how much percent execution is completed. There should be an icon or something which will display either execution coverage in % or graphically.
It should display same when execution is scheduled from Ranroex Testsuite as well as if it is scheduled using batch file.

In order to create large PDF Reports, we need 64-bit memory allowance. However if I change this for my nodes to run on 64-bit my team cant debug anymore, as the CSPROJ is controlling both the target and the testclasses the scripts will add (so they cant ignore it).

To get around this, having 64-bit debugging support would be great.

As a company with different department and different needs, we decided to adopt BDD style scenario, so that business expectation are fulfilled correctly by development. It would be great if we could write BDD scenario that can be converted in Ranorex style inside the application itself. The idea is to write the Given, When, Then, and behind the scene handlers are created that will contain the code that will effectively run the test.

Manage results and executions in a more efficient and dynamic way. So with the publications and issue creation on Jira, the bug-checking job gets much faster