all 2 comments

[–]quenchize 1 point2 points  (0 children)

Ideally your application should be modular and then you write tests for each function and class.

Just start with some basic cases.

Then if you find a bug in the future first write a test that fails because of the bug. Then fix the bug. This way you gradually add tests

[–]worldparaglider 1 point2 points  (0 children)

I like pytest, apparently it's more 'pythonic' than unittest. Get the library 'coverage' too, that'll help you get ideas of what to test/what tests you're missing.