1–5 of 5 posts
I'm trying to become better at unit testing (especially in python) but I'm struggling to write effective tests or even just writing tests on functions that return nothing or need to be mocked. I read articles on the subject, watched conferences and read the documentation of py.test and I still have difficulties because usually test cases shown are really simple. Would you have interesting resources to share on the matter?
Thanks a lot
It is unclear to me what do 'better at unit testing' means for you.
It is unclear to me what do 'better at unit testing' means for you.
I mean, I a real beginner on that part and I have difficult to write efficient an relevant tests when it comes to test functions or methods that returns nothing, when it comes to mock a database, test a socket connection to give you some ideas where I'm struggling.
If you've listened to 'uncle' Bob Martin, you've probably seen him advocate writing tests first (if you haven't listened to him and you're interested in testing, he has an experienced view whether or not you wind up agreeing with him). Writing tests before the code means that the code will either be testable or it will be wrong (it might be testable and still wrong but there's a chance that the tests will show that).
Anyway, I suppose my point is that if I don't know how to test my code, the problem is probably the quality of my code not my knowledge of testing. Perhaps complex testing techniques are a code smell for complicated programs. Or not.
Earlier quoted context omitted.
I mean, I a real beginner on that part and I have difficult to write efficient an relevant tests when it comes to test functions or methods that returns nothing, when it comes to mock a database, test a socket connection to give you some ideas where I'm struggling.
One of the benefits of writing tests is that helps a programmer avoid writing code that is hard to test (and by implication hard to measure correctness). And one of the goals...or maybe the only goal is to use tests to improve the code. Based on your description, a first order approach might be to write (and/or refactor) your code into a testable form. And by 'testable' I mean what your current skill set allows you t…