-
Notifications
You must be signed in to change notification settings - Fork 150
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
new step @then(u'{something:ANY} must be enabled') #123
Comments
Hi @vrbcntrl, Thanks for providing improvement to the tool :) Few things that will cause problems ;
Thanks again! |
Yes, understood and agree with you. Please let me know when you get a chance to incorporate this changes in to the encryption enabled steps. I am also wondering if you could add/modify the encryption enabled step to accommodate both encryption_at_rest and encryption_in_flight use cases for a same resource. so to check if these 2 encryption properties are enabled, I had to write
However, I am wondering some thing like below would make it more easy
to support this we might need to update the encryption enabled step some thing like this
any thoughts?? |
so, I cam up with this generic step in place of encryption enabled step, please let me know if it make any sense to you :)
I have tested the above step with my below BDD features
Test results are shown below:
|
Hard to say anything since this is not a Pull Request. All code changes must come via Pull Request, not via Issues :) I think I understood what we are aiming for, will have a look |
thank you! |
Could you please have a test with Thanks for the PR again! 🎉 |
Tested the changes with Thanks! |
Hi @eerkunt
We came across a pretty common use case and found that the corresponding step is not available, so I have created the new step by referencing the encryption enabled step, hope it will be useful.. :)
Let me know if the step needs any improvements...
BDD:
Step:
The text was updated successfully, but these errors were encountered: