Let us know your feature requests - also vote for others.

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 variable x.

Unfortunately, it happens often that developers forget to manually remove the temporary values for the test suite variables before the test suite is released. While those values will not affect the actual execution of the test in operation, they can irritate the user because they are visible in the parameter list of the released test suite as well as in the test data section of the test report. In my organization we had several request / complaints from operations staff claiming that the test suites contain "wrong" test data. In fact, the test suites were fine but the operations staff did not realize that the values have no effect because they will be overwritten during execution. For a user that just runs the tests it is difficult do distiguish "real" test data from negligible values in the test suite.

Proposal: Add a flag/checkbox in each row of the parameter list of a test suite / test case (on sheet 'Data binding'). With this Checkbox, the developer can define whether the value he just set is temporary or final. Ranorex shall keep the temporary variable values only in 'debug' build configuration. When the build configuration changes to 'release', the temporary variable values shall be automatically removed so that the test suite is "clean" for the final user.

1 vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base