Reuse Testcases
Make it possible to use a testcase more than once in a testsuite, just as it is possible to reuse a recording or code module. This would allow more modular use of testcases.
Andreas Grasmüller
shared this idea
Thank you for your idea. We will take a closer look at it.
6 comments
-
loonquawl
commented
Would be very convenient to just use an instance of a Testcase, instead of the Testcase itself.
Would make everything much more easy to alter and service - especially if the user gets some say on the instance (have an instance of the testcase somewhere, in studio show that TC as it is, with checkboxes pre-enabled for every recording and module, so you can disable individual modules in that instance of the TC)
It would be like a cool module group, because module groups have that instantiation-goodness, but lack loopability and the possibilty of SmartFolders (which would provide conditionality) - the dis-/enabling of individual modules would just be another convenient twist on the general idea.
-
Uwe Matzen
commented
I agree as well. At the very least, SmartFolders shouldn't be required to be unique; or they could have a "Display Name" property that the TestSuite folder can be configured to display instead of Id.
-
Pavel Kudrys
commented
There is already a feature request for this:
http://uservoice.ranorex.com/forums/150109-ideas-to-improve-ranorex/suggestions/17132710-reuse-testcases
And it's something Ranorex folks already considering ;) -
Uwe Matzen
commented
Completely agree on this. I understand why testcase names should be unique,but with the addition of Smartfolders in 7.0, i becomes possible to simulate testcases with multiple configurable steps. But being forced to give them uniqiue names is pretty inconvenient.
-
Anonymous
commented
would be helpful if we could name different TC's in one TestSuite s same if the TC's are located in different folders
-
Pavel Kudrys
commented
Absolutely agree here! I often use the same TCs across my solution, but each TC needs its own unique name. And this is a real pain, because I often do same TC name-based magic in code (like enabling/disabling TCs or setting TC data range), which means I must not to forget to add each single TC name to my code ;)