DEV Community

Discussion on: Why Testing After Is a Bad Practice

Collapse
 
raibtoffoletto profile image
Raí B. Toffoletto

Totally agree! As someone who works for a very small company that has the practice of not writing any kind of tests, I have to fall to the practice of writing my test units when I have a bit of free time way after I wrote the code. I can feel I'm biased towards the code written and have to do twice the effort to imagine edge cases or scenarios I haven't thought about before. Hope this will change in the future.
Nice article 🎉

Collapse
 
mbarzeev profile image
Matti Bar-Zeev

Thanks!

Collapse
 
starswan profile image
Stephen Dicks

I think it's a bit sad that you say 'you have a practice of not writing tests' in a small company. You could change that with your next PR - try writing the tests first. You might just find that the job is quicker (yes really!) because you get fast feedback on whether your code solves the problem or not, rather than testing everything manually.

Collapse
 
raibtoffoletto profile image
Raí B. Toffoletto

It's VERY sad... They basically told me not to 'loose time' with it... I'm trying bit a bit show other ways to them...

Thread Thread
 
mbarzeev profile image
Matti Bar-Zeev • Edited

And if that does not work out I think you should maybe consider your continuing of professional career path with them. If you consider testing and TDD a must-have tool for you to do your work well, you should look for an employer who acknoledges and respects that.

Thread Thread
 
raibtoffoletto profile image
Raí B. Toffoletto

Yes, that's the plan. 😉