Do you make Unit Test in your side projects?

It really depends, right?
For projects where you are only testing the grounds, early MVP - there is a big possibility that your architecutre code will change. Then I would suggest to wait, but be ready to add tests the moment you feel like you got a 80/20 and the goal of the MVP is starting to mature.
If you are spliting everything to small packages then you can add tests even earlier.
If you know that you are not very good with test disipline, then start doing TDD, it's hard but you will start being faster overtime.
Last point, it also depends on the project, if you are designing it thoroughly and know that it is mission critical then tests are probably a go to.

Say something nice to vgmartinez…

1

It really depends, right?
For projects where you are only testing the grounds, early MVP - there is a big possibility that your architecutre code will change. Then I would suggest to wait, but be ready to add tests the moment you feel like you got a 80/20 and the goal of the MVP is starting to mature.
If you are spliting everything to small packages then you can add tests even earlier.
If you know that you are not very good with test disipline, then start doing TDD, it's hard but you will start being faster overtime.
Last point, it also depends on the project, if you are designing it thoroughly and know that it is mission critical then tests are probably a go to.

agam

·
6 years ago
·