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
Expand Setup Tests #131
Expand Setup Tests #131
Conversation
@dmitrypolo Will review today, thanks! |
@dmitrypolo When I run
Any insight? |
I had the name backwards, for the assertion, can you please try again? If it fails on the temp file creation then I might have to look into it more as it might be a difference between |
seems like it is an issue between Linux and Mac, just hopped onto a Linux box and verified the same errors are happening. I will investigate and submit a fix when ready. Thanks for pointing this out. @isms |
@isms I figured out the issue and tested on Linux and all tests came back good.
The issue is with how the project is created on Mac/Darwin vs. Linux. On Mac when you supply a dictionary of arguments and provide it a project_name, i.e |
Merged, thanks @dmitrypolo! |
Part of our Data Days for Good initiative was to work on this repo. One of the requested additions was fleshing out the setup tests a little bit more to test for what would happen if user input was introduced. This was mentioned by Isaac. I have separated out the fixture and put it in it's own file, which is discoverable by
pytest
and mentioned in the docs. I have also increased the scope of creating the temp directory to be a class scope so it doesn't have to create it and tear it down after every function call. Lastly I also test for certain conditions given user input.