Re^3: To parens or not parens in chained method calls

Replies are listed 'Best First'.
Re^4: To parens or not parens in chained method calls by Your Mother (Archbishop) on Feb 16, 2017 at 18:56 UTC
I probably write too many unit tests. You have me confused with someone else; which is pretty hard to do since I frequently answer testing related questions here.	[reply]
Re^5: To parens or not parens in chained method calls by stevieb (Canon) on Feb 16, 2017 at 23:04 UTC
That's one thing we definitely have in common. I'm not happy until I have 100% coverage, in numerous different ways, and often go way overboard.	[reply]
Re^5: To parens or not parens in chained method calls by Anonymous Monk on Feb 16, 2017 at 18:58 UTC
Test envy? XD	[reply]
Re^6: To parens or not parens in chained method calls by Your Mother (Archbishop) on Feb 16, 2017 at 19:04 UTC
:P I throw down as many tests as I can think of as soon as they occur to me and extend whenever I notice a change or something I missed, which means I break best practices and cause duplication and such too often. Computer is my hand-servant though. I’m not concerned about overworking it despite knowing I could write tests more intelligently and strategically. I’ve rarely come to regret writing too many tests though and I have often regretted writing too few.	[reply]
Re^7: To parens or not parens in chained method calls by stevieb (Canon) on Feb 16, 2017 at 23:13 UTC