Thanks Pavel for the idea to do it the other way round .
Now I have the validation in one Module with a code module which only enables the next Module if the condition is met.
Enabling a module via code works perfectly fine and has no side effects to the report.
Search found 6 matches
- Fri Nov 25, 2016 4:55 pm
- Forum: How To …
- Topic: Stop running module on condition
- Replies: 15
- Views: 7164
- Fri Nov 25, 2016 1:26 pm
- Forum: How To …
- Topic: Stop running module on condition
- Replies: 15
- Views: 7164
Re: Stop running module on condition
Just noticed another problem with this:
The report has no entries after the module that has been stopped through code except for the Headers and the last Teardown doesn't get executed.
The report has no entries after the module that has been stopped through code except for the Headers and the last Teardown doesn't get executed.
- Thu Nov 24, 2016 3:50 pm
- Forum: How To …
- Topic: Stop running module on condition
- Replies: 15
- Views: 7164
Re: Stop running module on condition
Maybe we can live with that for now.
Still think it is a Bug to mark it as failed when it just has been (partially) skipped.
Still think it is a Bug to mark it as failed when it just has been (partially) skipped.
- Thu Nov 24, 2016 3:37 pm
- Forum: How To …
- Topic: Stop running module on condition
- Replies: 15
- Views: 7164
Re: Stop running module on condition
Problem is: converting the recorded actions into code is not an option. I need this logic in a lot of modules and someone with no coding skills needs to be able to maintain the modules. In general the method I used does work, except for it always returning that the module failed. Weird thing is: alt...
- Thu Nov 24, 2016 1:45 pm
- Forum: How To …
- Topic: Stop running module on condition
- Replies: 15
- Views: 7164
Re: Stop running module on condition
With Ranorex 6.1.1 it doesn't work either...
- Thu Nov 24, 2016 12:59 pm
- Forum: How To …
- Topic: Stop running module on condition
- Replies: 15
- Views: 7164
Stop running module on condition
I'd like to stop a currently running recording module based on a condition. My solution was to add a user code at the beginning of the recording module, if the condition is true it should validate something and then stop the current module, if false execute the module normally. C# Code in called use...