-
Notifications
You must be signed in to change notification settings - Fork 160
tests: refactor systests using pytest #476
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
Conversation
Refactor to use pytest fixtures Toward #475.
Refactor to use pytest fixtures Toward #475.
Refactor to use pytest idioms. Toward #475.
Refactor to use pytest idioms. Toward #475.
Refactor to use pytest idioms. Toward #475.
Refactor to use pytest idioms. Toward #475.
Make it return the actual credentials for use in testcases.
300e270
to
97fc701
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.
LGTM👍 Thanks @tseaver for making the big move of splitting the system test. Appreciate the iterative approach and review tips. It was nice to follow commit-by-commit.
Systests under Python 2.7 fail here because googleapis/python-test-utils#36: Options:
|
* Move systests from monolith to new, more focused modules. * Refactor systests to use pytest fixtures. Closes googleapis#475
* Move systests from monolith to new, more focused modules. * Refactor systests to use pytest fixtures. Closes googleapis#475
Closes #475
Note to reviewers: this PR touches every bit of
tests/system
, splitting the monolithictests/system/test_system.py
into coherent pieces and refactoring them to use pytest fixtures. It is likely easiest to read commit-by-commit, at least until the pattern becomes clear.