Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: Improve the documentation of the Suite Setup and Teardown behaviour #176

Open
damies13 opened this issue Feb 16, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@damies13
Copy link
Owner

Improve the documentation of the Suite Setup and Teardown behaviour in default state and when TestRepeater setting are enabled


[09:15]crashfile:

Is it recommended to have like a suite setup that runs prior to any test itself?

This is to dataload values that would be use by the test?

similarly at the end it will run a suite teardown?

[12:57]damies13:

The behaviour of Suite Setup and Teardown changed with v1.2.0. By default it still behaves the same as previous versions, but changes if you enable the optional TestRepeater setting.
see documentation here: https://github.com/damies13/rfswarm/blob/master/Doc/rfswarm_manager.md#test-repeater
and Feature request here: #133
This question made me realise the documentation for this could explain it better

[12:59]damies13:

Short answer, you can use Suite Setup and Teardown, but how often they run will be determined by if you enable TestRepeater or not

[13:04]damies13:

If you want it to only run once (even if the test fails, the robot stops and another robot runs a new suite of the same test case) then you can use IF with ${RFS_ITERATION} to only run on iteration 1
If you only want 1 robot to run it once, you can combine ${RFS_ITERATION} with ${RFS_ROBOT}

@damies13 damies13 added documentation Improvements or additions to documentation enhancement New feature or request labels Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant