You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 9, 2022. It is now read-only.
I would like to discuss the topic of unit testing again. I think it would be particular important if contractors start working on the same code base. In the beginning it seems like a huge investment to go that round but it really does pay of, especially if you rewrite or replace certain parts of the code.
I am not very strict with test-driven development. Strict would be, 1. create a spec, 2. write a test for the spec, 3. write the unit. I usually do 1. write a unit, 2. write a test that confirms the unit working (sometimes not before I actually get to reworking the unit). 3. improve and rework the unit (as needed).
Sorry, if I am way behind and you are doing this already but let's just discuss it anyways.