-
Notifications
You must be signed in to change notification settings - Fork 75
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
Fix validation warning in tests #124
Conversation
So.....the presence of that invalid value actually served as a test of the warning code. sigh |
How would you feel about using pytest's warning support instead? |
Hmmm...I'd rather add a new test to |
Oh man...I think I see it now 👎 |
Separate test is fine, but then you need to swallow the warning in the other test. |
Oops...that comment was for another issue. Yes, a separate test that triggers and swallows the warning using pytests warning support. |
Can you add that here so we don't drop (meaningful) coverage? |
Yep, will do - just need to get aws going again laughs I'm running single threaded tonight. |
So |
So it looks like pytest-catchlog is the answer (it's on PyPI and conda-forge). If you're not up for adding it, I can do it. |
I found that, too. I can add it in - I just wanted to talk to you about it before doing so. Let me update the PR. |
We get a validation warning in our test suite due to an attribute added to a catalog that is not under our control.
We get a validation warning in our test suite due to an attribute added to a catalog that is not under our control.