Ideas to Improve Ranorex

Thank you for sharing your thoughts with us at Ranorex Uservoice.

  1. Manipulation of Reports and JUnit file

    Like my question in this post:
    https://www.ranorex.com/forum/test-case-classname-renaming-t11952.html

    It would be great to manipulate attributes of test cases inside a report, especially in the JUnit export file.

    When importing the JUnit report into our ALM system it generates a unique name from the test cases name and classname.

    In case of databinding (e.g. Excel) these names end with "DataIteration x" where x stands for the Excel row/iteration index.

    When the sorting of the Excel changes or lines are moved/deleted/added, the DataIteration index doesn't match anymore. That would destroy the ALM data.

    It would be great to have the ability to set…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Remove temporary test suite variable values in Release configuration

    Test suite variables are often used to pass values from one test case to another. For instance, a producer test case A writes a value in a variable x and a consumer test case B (which belongs to the same higher level test case) reads the value afterwards.

    During test case development or debugging, one often fills test suite variables with temporary values in order to save execution time. For instance, if a developer wants to execute test case B without having to execute test case A first, he can do so by assigning a (temporary) default value to the…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Validation fail User definable

    the user would have the choice to make the test fail and stop at the failed validation point or throw a warning of some sort and continue with the test.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. TestSuite.Current.Parameters["paramName"] is null when calling Ranorex.Core.Testing.TestModuleRunner.Run(myPage);

    TestSuite.Current.Parameters["paramName"] is null when calling Ranorex.Core.Testing.TestModuleRunner.Run(myPage); Need to have a way to init TestSuite by default in the constructor somewhere.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Ability to test Apple TV and Android TV

    It would be great if you could make Ranorex able to instrument Apple TV apps and Android TV apps and make the automation run on either a physical device or an emulator.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. module browser: allow to create folders, delete items, move items

    The useability in the module browser is very poor: It is not possible to create folders, move modules or delete modules.
    For theese operations I have to use the projects browser.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Pass dynamic number of arguments from recording module to usercode

    Recording module gives so much clarity to testers (especially those who do not code) when used properly. It is very readable however, it only supports userCode with fixed number of parameters. It would be good if Ranorex could support passing dynamic number of arguments and pass them properly to usercodes (at least for the native datatypes) . In a recording module one test might have this

    Get Item A
    Get Item B
    Verify A B

    then another module might have
    Get Item A
    Get Item B
    Get Item C
    Verify A B C

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Retry Count setting should have greater priority over Error Behavior setting or we need a new Behavior setting

    In reference to this URL:

    https://www.ranorex.com/help/latest/ranorex-studio-fundamentals/test-suite/running-tests/#Configureautoretry

    When the Error Behavior setting is set to STOP and the retry count is NON-zero, when a minor test error happens I feel that the retry count should be honored and if all the retries have been exhausted only then should all testing STOP per the behavior setting.

    Currently (v8.3.0 and lower) this is not the case and if you set retry to > 1 the test will just STOP on the 1st error it hits with no attempted retry.

    I would like to see the ability to bump the retry count setting as…

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
1 2 17 18 19 21 Next →
  • Don't see your idea?

Ideas to Improve Ranorex

Feedback and Knowledge Base