initial infrastructure for smoke tests#176
initial infrastructure for smoke tests#176graysonarts merged 3 commits intotableau:developmentfrom graysonarts:add-inital-smoke-infrastructure
Conversation
| __pycache__/ | ||
| *.py[cod] | ||
| *$py.class | ||
| test.junit.xml |
There was a problem hiding this comment.
What's gonna end up in here?
There was a problem hiding this comment.
It's the junior version of the results that our internal build system needs for test runs
There was a problem hiding this comment.
Junit not junior
There was a problem hiding this comment.
You'll get to be a grown-up results file someday, little test.junit.xml
| #parentdir_prefix = | ||
|
|
||
| [aliases] | ||
| smoke=pytest |
There was a problem hiding this comment.
This means smoke will run unittests AND smoke, right?
There was a problem hiding this comment.
Yup. I have smoke running both the test directory and the smoke directory. Test will only run the test directory
| tests_require=[ | ||
| 'requests-mock>=1.0,<1.1a0' | ||
| 'requests-mock>=1.0,<1.1a0', | ||
| 'pytest' |
There was a problem hiding this comment.
I was wondering when we'd eventually end up moving beyond unittest as our test runner :P
|
Approach seems solid in terms of a runner. Feature requests (may not be our first pass):
|
|
I checked this out locally and was able to run everything, though it was mad at me that I was using a version of requests-mock that was too new (1.2 -- latest is 1.3). Why pin to 1.1? |
|
@t8y8 oh, hrm, we should pin to 1.x not 1.1.x. I'll fix that. |
|
@t8y8 okay with me merging in this bit? I need it for integration work |
* initial infrastructure for smoke tests * trying to fix travis errors by not pinning the version * fix pinning to major version, not minor
2 participants
This isn't complete, but an idea I'm playing with. @t8y8 thoughts?