Switching from nosetests to py.test. - #2241
Conversation
Sorry, something went wrong.
|
I also created https://github.com/GoogleCloudPlatform/gcloud-python/tree/use-pytest to spawn https://ci.appveyor.com/project/dhermes/gcloud-python/build/1.0.617.use-pytest Will delete after this is verified. |
Sorry, something went wrong.
| @@ -1,2 +0,0 @@ | |||
| [nosetests] | |||
| exclude-dir = system_tests | |||
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
| commands = | ||
| {[testing]covercmd} --cover-min-percentage=100 | ||
| {[testing]covercmd} | ||
| coverage report --show-missing --fail-under=100 |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
In the process, fixing some PATH issues in "gcloud._helpers" (path separator was explicitly provided, rather than using "os.join"). Also the the associated tests were refactored with more mocks so that they depend less on the OS.
|
The continuous-integration/travis-ci/push check came up because I pushed theGoogleCloudPlatform/gcloud-python:use-pytest branch to this project. (I did it so that the AppVeyor tests would spawn, mentioned above.) That job didn't fail, I just canceled it, since it would be repetetive to run both PUSH/PR for the same exact code. This should be ready to merge if I can get an LGTM. |
Sorry, something went wrong.
|
Lgtm On Fri, Sep 2, 2016, 4:49 PM Danny Hermes notifications@github.com wrote:
|
Sorry, something went wrong.
No description provided.