Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Keyword teardown functionality #711

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.

Sign up for GitHub

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

Jump to bottom
Closed
spooning opened this issue Jun 29, 2014 · 6 comments
Closed

Keyword teardown functionality #711

spooning opened this issue Jun 29, 2014 · 6 comments
Assignees
@yanne
Labels
enhancement priority: high
Milestone
2.6

Comments

@spooning
Copy link
Contributor

Originally submitted to Google Code by @pekkaklarck on 19 Nov 2010

It would be useful to allow user keywords to have their own teardown. This teardown keyword would be executed even if any of the keywords in the user keyword fails, and would naturally be executed as the last keyword if all other keywords pass.

This functionality would be especially useful with the new test template feature when a test has multiple "sub tests". The keyword used as a template could have teardown to make sure that the next "sub test" starts from a known state also if there are failures. Another good use case is taking a screenshot or doing cleanup if certain action fails.

I hope this feature can be included already into RF 2.5.5.
@spooning
Copy link
Contributor Author

Originally submitted to Google Code by @pekkaklarck on 19 Nov 2010

To make it possible to e.g. take a screenshot ONLY when a keyword has failed, we need to enhance Run Keyword if Test Failed so that it could also be used inside the new keyword teardown.

@spooning spooning added this to the 2.6 milestone Jun 29, 2014
@spooning
Copy link
Contributor Author

Originally submitted to Google Code by @yanne on 6 May 2011

This issue was updated by revision d2930be57486.

Still need to add tests for dry run and update user guide.

@spooning
Copy link
Contributor Author

Originally submitted to Google Code by @yanne on 6 May 2011

This issue was updated by revision 7b737777349a.

@spooning
Copy link
Contributor Author

Originally submitted to Google Code by @yanne on 9 May 2011

Added documentation to user guide in revision d1b3adce8af8.

@spooning
Copy link
Contributor Author

Originally submitted to Google Code by @pekkaklarck on 9 May 2011

This issue was updated by revision 50acde4051d4.

Docs look good. Did a small enhancement and fixed the example, though.

@spooning
Copy link
Contributor Author

Originally submitted to Google Code by @pekkaklarck on 13 Jun 2011

Included into 2.6 alpha 1.

@pekkaklarck pekkaklarck mentioned this issue Apr 24, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yanne yanne

Labels
enhancement priority: high
Projects
None yet
Milestone
2.6
Development

No branches or pull requests
2 participants
@yanne @spooning