-
Notifications
You must be signed in to change notification settings - Fork 104
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
IPS & ood-portal-generator: Change whitelist to allowlist #583
Conversation
Deals with ips and ood_portal_generator
f1a3dd8
to
26d70d7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fixed the merge conflict and rebased to master. I think we're good with this, there's a test case testing the current config and the previous config against the same file, so it's in good shape.
not only does this add tests, but starts a testing infrastructure around testing input and output fixture files.
Can I get a second pair of eyes on this @treydock? I added test cases that utilize fixture files rather than stubbing |
Do you have any thoughts on the testing strategy I'd like to move towards? Input fixture files are small enough and won't need to change alot - but output fixture files would need changing across potentially all of them. That's kind of the situation we're in now, but I feel like this library's purpose is to write a file given an input file - so let's test those boundaries. |
I think it makes to stub files and test whole files since that's how the application is operating, it works off of files and writes out whole files. The huge benefit to validating entire files is to ensure we know 100% how certain changes affect the entire templates. |
Deals with ips and ood_portal_generator