-
Notifications
You must be signed in to change notification settings - Fork 122
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
Use pytest fixtures #948
Comments
Just a note that the fixtures currently defined in conftest.py start with |
Another note: per #1001 (comment), we should find meaningful names for each test fixture that is created from the test cases. Right now the test cases are numbered 1-8, but if we dig in to each test case, we should be able to come up with a more descriptive name that makes it clear what scenario(s) test case is trying to exercise. |
* refactor: normalize import style #1259 * refactor(tests): modernize version extension tests - #993 - #948 * feat: add experimental to version ext * feat: version is optional in version extension * refactor: test import naming, ext * feat: catalog extensions * refactor: import style * feat: add history media type * feat: separate BaseVersionExtension * feat: impl migration * doc: fixups * chore: update changelog * fix(tests): mark some extra vcrs * fix: pop_if_none on deprecated
Since pystac is switching to
pytest
for testing (#939), we should look at using pytest's fixtures.The text was updated successfully, but these errors were encountered: