-
Notifications
You must be signed in to change notification settings - Fork 15
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
setting defaults for tokens #116
Comments
@spoore1 defining the tokens on the module level does not help? Or you are looking for a solution that will be global so every module would inherit it? |
Can I do that? Add a docstring for the module with tokens? Yeah, actually, that's better. Tokens at the module and class level would both be very useful I think. At the moment, I see them listed as Unexpected tokens:
|
@omaciel you are correct. I had misunderstood the help listing for that. Looks like that works now:
That's awesome. I think this can be closed. Is this in the doc? If not, might be a good example to add. Thanks, |
We need to clarify the documentation |
This is briefly explained in http://testimony-qe.readthedocs.io/en/latest/#test-case-docstring-format. But examples are not shown on how to override the defaults. +1 to adding examples. This can be addressed in #119. @spoore1: If you want to contribute to this doc, please feel free to. Otherwise it will be worked eventually. And please close this issue if you are okay. |
It would be useful to be able to set default vaults for tokens that would apply to all test cases when testimony runs. If I have a test suite with a lot of test cases where several tokens are set identically, it would be helpful to set that outside the tests.
A config file alongside the tests maybe? Or command line options? Or maybe a new token to pull that info from a config file?
Keeping things flexible, if a token is defined in a config, it would be overridden if defined in a test case.
Does that make sense?
The text was updated successfully, but these errors were encountered: