Test-Driven (Development)

Why is it so complicated?

The root of the problem

Without (a solid) experience in testing, developers can have a hard time while trying to apply testing in general as part of their daily job. I think it’s not simply because of the topic’s complexity, but because they are used to write code that is hard to test.

The complexity here is not on writing tests itself, but the habits that the developers have to change to create software that is easy to be tested.

Writing tests for already working software (mainly when it was done without considering testing at all) translates as something boring, next to useless, usually accompanied by a lack of motivation, blaming the wrong subject in this context: “the tests itself are reducing my speed”.

In a domain context, if a piece of software logic is hard to be tested, the problem is not the test, but the code which wasn’t well written.

There are already hundreds of tutorials, books, and documentation about testing, but I can share my experience and how I do apply this great (and must) philosophy in my daily work.

Read full blog post: https://chemaclass.com/blog/test-driven-development/