Arnold

My feedback

  1. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  4 comments  ·  Ideas to Improve Ranorex  ·  Flag idea as inappropriate…  ·  Admin →
    Arnold commented  · 

    also, need force stop, clear data, and/or Wi-Fi access to the Android shell

    Arnold supported this idea  · 
    Arnold commented  · 

    Will this be added to Ranorex 9.x?
    This is a critical feature for Automated Android testing without manual intervention.
    This can be accomplished with adb and a USB connection, but Ranorex's handling of adb on USB is unreliable, e.g. adb daemon goes offline, when using a Wi-Fi endpoint for the majority of testing. Which requires manual intervention, e.g. USB disconnect/re-connect, i.e. not a server issue with adb, but an adb daemon issue.

  2. 26 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Ideas to Improve Ranorex  ·  Flag idea as inappropriate…  ·  Admin →
    Arnold supported this idea  · 
    Arnold commented  · 

    I second the request, any response from Ranorex?

  3. 15 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ideas to Improve Ranorex  ·  Flag idea as inappropriate…  ·  Admin →
    Arnold supported this idea  · 
  4. 32 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Ideas to Improve Ranorex  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input.

    We have talked about this in the past before. The problem with multiple data sources for one test case is actually the way the iterations work and how the iterations over the test case should be handled. This could potentially get very confusing.

    However, we will evaluate if there is a solution that will both make sense and won’t be too confusing with the way iterations work with data connectors.

    Best Regards,
    The Ranorex Product Management Team

    Arnold supported this idea  · 
  5. 28 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Ideas to Improve Ranorex  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input.

    We know that our documentation is far from perfect. A better API documentation is the highest-voted feature here in the user voice.

    On the other hand, we have released our new user guide several months ago. The new guide is far more detailed than the old one, and we have started to provide more material than ever before.

    A possible next step could be an offline version (export) of the user guide. Would this be interesting for you, or are there more pressing topics in our documentation?

    We would appreciate some input.

    Best Regards,
    The Ranorex Studio Product Management Team

    Arnold commented  · 

    This is extremely important.
    The current documentation resources are either out of date or require extreme effort to find.
    E.g. forum is too difficult to search in a short amount of time, and Ranorex's help site search results are too generic, too basic, too tutorial, and never get to the detail.
    Even Ranorex's support engineers can't find the information and have to go their devs.
    This is expected with open source software, but not commercial software.
    Luckily Ranorex customers have support from an excellent staff of support engineers.
    I see needing their support often in the future.

    Arnold supported this idea  · 
  6. 135 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Ideas to Improve Ranorex  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you all for bringing this to our attention. This topic is currently the number one topic in our User Voice. We are aware that our API documentation is far from perfect, and we see the value in improving it ourselves.

    We are currently investigating the options we have for this API documentation. We are not sure yet about details like the format or the platform. Additionally, there are some parts of the API are not meant for public use and only enable Ranorex Studio to do specific things, etc.

    This means, we are aware of the issue and we are trying to figure out how to tackle this best.

    Best Regards,
    The Ranorex Product Management Team

    Arnold supported this idea  · 
    Arnold commented  · 

    Yes, please.
    Plus Ranorex documentation needs a refresh. Most important for mobile.
    We need a fully documented, with technical details manual.
    Not a getting started guide, A.K.A. user guide, with hints, but no explanation or background.

Feedback and Knowledge Base