688 reputation
610
bio website partialclass.blogspot.com
location Burlington, MA
age 41
visits member for 3 years, 8 months
seen Oct 28 at 17:38

I program in C# / ASP.NET professionally, with MSSQL on the database side. For fun I work on iOS apps both in Objective-C and MonoTouch. I also still remember a lot from my years working with Lotus Notes.


Apr
8
awarded  Yearling
Jul
9
comment When is it appropriate to not unit test?
@Sam, for what it's worth: partialclass.blogspot.com/2013/07/thoughts-on-unit-testing.html
May
21
awarded  Favorite Question
Apr
8
awarded  Yearling
Mar
4
comment When is it appropriate to not unit test?
@Phil, thanks. I agree. If I could sum up all I've learned on this topic since writing this post it would be this: Don't Make Assumptions. That goes for TDD people as well as non-TDD people. There is lots of good advice here, but still TDD was completely wrong for the situation I was in when I originally asked the question. Looking back I think the question was too vague. Probably the only universal thing we can all agree on is that testing is always necessary. What is most appropriate (and efficient) for a particular project will always depend on that project.
Mar
1
awarded  Notable Question
Apr
8
awarded  Yearling
Aug
23
awarded  Popular Question
Aug
23
awarded  Good Question
May
23
comment When is it appropriate to not unit test?
@Rein, what exactly is the "available evidence?" Please elaborate.
Apr
29
comment When is it appropriate to not unit test?
@Rein Henrichs - Of course I made the number up, it was a hypothetical statement. I'm making the point that TDD adds a significant amount of time to a project, and I have to consider whether I'm going to get something of equal or better value in return. You don't have to convince me on the values of TDD, I'm convinced. But it is not a panacea.
Apr
27
comment When is it appropriate to not unit test?
Good answer. One of the few that really answers my original question. I have submerged myself into the world of testing since writing this post (I like it btw.) I need to understand it more before I can truly know when to use it (or not). For many of the reasons stated here I would prefer to use it all the time. But it will ultimately depend on how much faster I get at it, because in the end it is a gamble of my time, which is under my company / client's control, and often they focus on the bottom corners of the project triangle: en.wikipedia.org/wiki/Project_triangle
Apr
11
answered How many programmers makes a company small / medium sized / large?
Apr
11
comment When is it appropriate to not unit test?
There are a ton of great answers here, but I'm choosing this one because the answer and comments most closely address the original question I posed: When is it appropriate to not unit test?
Apr
11
awarded  Scholar
Apr
11
accepted When is it appropriate to not unit test?
Apr
9
comment When is it appropriate to not unit test?
Reminds me of the saying my dentist has: You don't have to floss all of your teeth, just the ones you want to keep.
Apr
9
comment When is it appropriate to not unit test?
Very interesting benefit. I kind of like that.
Apr
9
awarded  Commentator
Apr
9
comment When is it appropriate to not unit test?
Wow, THE Uncle Bob? It's great to get your thoughts here. I agree with you on the benefits of TDD, there really is no argument to be had there. The question is about the investment of time and the ROI. It isn't silly for me to consider these things. Imagine a project will take me 50% more time to finish with TDD than without, and the fairy tells me it will only save me 10% time over manual testing in the lifetime of the project. That might seem like a fantasy, but I see it as entirely plausible with certain projects.