Skip to content

Conversation

@Flamefire
Copy link
Contributor

Using pytest allows for faster writing of tests due to easier syntax as well as including e.g. coverage and other pytest plugins

@vsoch
Copy link
Member

vsoch commented May 29, 2019

hey do you want me to fix the linting issues? Happy to :)

@Flamefire
Copy link
Contributor Author

No it's fine. Marked the PR as WIP because I wanted to try how it works on CI, I'm not yet done.

@vsoch
Copy link
Member

vsoch commented May 29, 2019

Alrighty - I'm well into the refactor for the recipes, I'll take the fix for #111

@vsoch vsoch mentioned this pull request May 29, 2019
@Flamefire Flamefire force-pushed the pytest branch 4 times, most recently from 4a36b4e to 4943bb1 Compare May 29, 2019 16:12
@Flamefire
Copy link
Contributor Author

I'm off till monday. You can take this over to see if you can fix the python2 failure. Not sure why the filter doesn't work there...

@vsoch
Copy link
Member

vsoch commented May 29, 2019

You got it! Thanks @Flamefire, enjoy your time off.

@Flamefire
Copy link
Contributor Author

Just got an easy idea: use a pytest decorator to skip this if singularity 2. Then you only need 1 cmd to run all tests.
I suggest you base your changes on this and I'll fix this monday.

@vsoch
Copy link
Member

vsoch commented May 30, 2019

okay back in business, home safely! Starting to work on this now.

@vsoch vsoch mentioned this pull request May 30, 2019
@vsoch vsoch merged commit 8ccdd06 into singularityhub:master May 30, 2019
@Flamefire Flamefire deleted the pytest branch May 31, 2019 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants