If it were a side project using technology where I was already familiar with the testing tools, I will. I really like testing in environments I'm familiar with. But, for whatever reason, testing tools take me forever to pick up, so I might forego it in low-risk side projects.
Most testing tools are bloated, in my opinion - it shouldn't take very long to pick up a testing tool, if the tool leverages your existing knowledge of the language, but most test frameworks replace everything with assertion functions.
Try something like tape.js for testing - it's very small, and has only a few assertions that are necessary to do things like deep comparison. It seems to follow the Go language testing philosophy of "less is more" and leveraging what you already know.
I love that! Writing tests is so much more intuitive, and your tests will be much easier for someone else to read.
If it were a side project using technology where I was already familiar with the testing tools, I will. I really like testing in environments I'm familiar with. But, for whatever reason, testing tools take me forever to pick up, so I might forego it in low-risk side projects.
Most testing tools are bloated, in my opinion - it shouldn't take very long to pick up a testing tool, if the tool leverages your existing knowledge of the language, but most test frameworks replace everything with assertion functions.
Try something like tape.js for testing - it's very small, and has only a few assertions that are necessary to do things like deep comparison. It seems to follow the Go language testing philosophy of "less is more" and leveraging what you already know.
I love that! Writing tests is so much more intuitive, and your tests will be much easier for someone else to read.
Thanks Ben, I see your point! 🙂
Same. When I'm building something small to learn a new technology I forego it.
If it's a bigger side project I plan to develop for a while I'll add static typing and selective tests for modules that seem fragile.
Not a religious tester by any means. Haven't actually been at a company yet that required tests so maybe I have not seen the light.
Thank you, Natti! Good to see that most devs go for tests, but don't do over-testing!