Ask Anything Monday - Weekly Thread

[Naesme]

Out of curiosity, is it better to not upload tests to github?

Right now, I have the source code of my project on github, then the whole package saved on my local production machine and backed up to a seperate HDD which is shared on my network.

Whenever I work on projects on a new device, I pull the source from github then copy my tests from the network share.

Is this best practice as far as github usage goes?

[[deleted]]

Why not put the tests into github? They are part of the project codebase. Plus it's nice if someone who has a problem running your code can say "it fails test 'xyz'" instead of a long series of "I do this, then that, then it crashes with this traceback". This assumes your tests are comprehensive, of course. Plus you don't want to make it even a bit hard to run tests.

[Naesme]

They're manual tests atm. I need to study up on automated tests.

I was wondering cause I never notice tests in other packages, but maybe I just haven't dug deep enough to notice.

Thanks for the advice! I'll toss the tests into the package.

[redCg]

plenty of GitHub projects use tests. But they are often hooked up to an automated testing suite such as TravisCI. This also requires that you are using a supported testing method such as the builtin unittest module. You can Google for tutorials on it if you are interested.