Comment #2 on issue 1710 by bryan.oa...@gmail.com: Add new built-in
keyword "Require test case"
http://code.google.com/p/robotframework/issues/detail?id=1710
If you're concerned about encouraging bad behavior, you could have robot
generate a warning whenever that keyword was used. You could provide a
command line option to silence the warning, which means the user has to
explicitly acknowledge that using that keyword is a bad practice (eg:
--no-warn-on-bad-practices)
I don't understand the idea of a test registering itself as a dependency
for something else. That means if you write a new test case that depends on
an old test case, you must also modify that old test case to register
itself. That seems like more work for the tester.
I understand your concerns. It's just that in my experience now in my third
company using Robot, dependencies are a fact of life. I'd rather document
them then have them hidden from view. Plus, the information can be
invaluable when trying to parallelize a test run.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
