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
Idempotence check? #141
Comments
Well in my ansible plugin i have a parameter idempotency_test set to false |
Cheers for the pointers - I'll take a look, and see if I can come up with something usable, and send a PR once it's working as expected. |
@madAndroid we have
|
Ah yes, thanks I hadn't spotted that, it will surely help when creating the idempotence test... but we'll still need to add code that executes a second test run and checks whether any changes have been made? |
@madAndroid this is already supported by test-kitchen (1.10+) test-kitchen/test-kitchen#1055 (comment) |
thanks for spotting test-kitchen/test-kitchen#1055 (comment) i should add these options to the docs and explain them. |
That's awesome - I'm very new to Test-Kitchen, and wasn't aware of that functionality - I'll try those settings, hopefully it will do exactly what we're looking for. |
closing this as i believe it is base test-kitchen functionality now. |
Thanks! On 17 Nov 2016 6:29 pm, "Neill Turner" notifications@github.com wrote:
|
Hi,
Is there a way to check whether a test run is idempotent within the same test run? Beaker has this functionality, and I've been wondering if there's anything similar in test-kitchen/kitchen-puppet.
I've attempted to use
detailed_exit_codes
, and this appears to cause the run to fail due to a non-zero exit code; would it be worth including a change that setsaccepted_exit_codes
to be used alongside this setting? This would also open us up to checking that exit code to see whether a subsequent run made any changes, and check for idempotence using that approach.Please let me know if this is an acceptable change, and I will look at sending a pull-request when I've got something that's usable.
The text was updated successfully, but these errors were encountered: