But as of Ranorex v8.3.3 there are a few of these that I need to DISable because they're failing due to changes in Ranorex itself.
Normally I use Run Configurations so that I can turn tests on/off as required. But with my day to day Ranorex development configuration I am always turning test folders on/off depending on whatever I'm working on.
How do you folks deal with test cases that you do not want to run (because they are guaranteed to fail and there is nothing you can do about that at the moment), but do not want to delete (because you hope that the underlying issue will be resolved)?
We've got another case where a feature in our AUT changed, so a set of tests for that feature need to be rewritten or significantly adjusted to suit. One whole year on and I'm still waiting on that duder to fix it up! I have our main test run configuration set to ignore that area, but again, I have to keep DISabling the tests in this area when I'm working on other things.
So I'm wondering if I'm approaching this incorrectly. I've just got so fed up of this problem - because I've been doing some Ranorex software upgrading recently I've been butting up against this annoyance repeatedly - that I've bunged in a code module to each of the failing test cases to skip them:
Code: Select all
TestSuite.CurrentTestContainer.Checked = false;