--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To post to this group, send email to robotframe...@googlegroups.com.
To unsubscribe from this group, send email to robotframework-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/robotframework-users?hl=en.
|
hide details 8:22 AM (34 minutes ago)
| ||||||||||||||||||||||||||||
That's how understood the question too.
> So is something like that achievable with current version of RF? I'm
> still new to RF. I know some frameworks have support for that but not
> all do. If not, then there are two approaches that I see:
>
> 1. Build new test suite (can't use current one "as is"), converting
> current one into data driven type test suite that will be repeating
> the test case for X data scenarios, matching the desired X executions.
This is possible but your log files could grow quite big. If you want
to try, using Test Template functionality with for loops makes this
pretty easy, although understanding the test requires quire a bit
advanced Robot knowledge:
***TestCase***
Example
[Template] Log
:FOR ${i} IN RANGE 100
\ Running round ${i}
> 2. Wrap RF around an external simple framework, like a batch file or
> shell/Jython/Python script where you pass it a parameter like run test
> X times or run indefinite. This script will then externally launch RF
> with given test suite and at end of test run, if runtime counter not
> equal to X or if run indefinite, relaunch RF again. Best implemented
> with a while loop, etc. in the script.
>
> In my opinion, I prefer option 2 above. Though that means someone has
> to put together the simple script to do that.
I prefer this option too. Keeping logic required for orchestrating
test execution is generally better kept outside the test data.
Cheers,
.peke
--
Agile Tester/Developer/Consultant :: http://eliga.fi
Lead Developer of Robot Framework :: http://robotframework.org