Then, as someone else pointed out, use black-box testing. Test only the public/external API. If your code is too complex to be tested this way, that's a sign of structure than needs to be refactored.

I don't think "it's the real world" will get much traction here - people that maybe started their careers the way you describe, changed their tune or left the business.

-----Original Message-----
From: Warren Stephens
Sent: Mar 2, 2020 12:54 PM
To: golang-nuts
Subject: Re: [go-nuts] Language proposal: labelled "with" statements to help make test code easier to write

The over-arching goal is for me to write tests more easily.  Not avoid writing tests.  I am not arguing against tests.

Though I am being a bit snarky when I see responses that seem merely to say "Use TTD or something similar and it will solve all your problems!" 

I have never experienced that writing tests at the beginning saves time.  I find it is always faster to not write them in the beginning.  Functionality typically changes 3 or 4 times before it "settles down" enough that writing tests makes sense to me.

Warren

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/26bba248-8a7c-453b-83ee-ae4043c7b4c1%40googlegroups.com.




-- 
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/276419913.2168.1583175779379%40wamui-fuzz.atl.sa.earthlink.net.

Reply via email to