Hi Mad,

Thanks for the feedback. I knew the technique, but I forgot the name. I tried twice just to know how it works, but I have to confess that never used it in a real project.

The reasons why I do not use them is because Approval Tests look for very low-level detail implementations, and they do not provide any significant insight about the intentions of the program. When you refactor with this technique, because you are checking just outputs, not behaviors, you may keep bugs or unintended features, limiting the growth of the application.

I rather prefer, and I have applied several times, the TDD approach. I do not care of having everything covered, because if I do not touch, why to bother, but the output are tests that talk about the application behaviors and not about the code.

But of course, that is my experience, do you have any experience in a different direction? I am open to learn :D