Comments on: To Test or Not to Test? That’s a Good Question. http://www.threeriversinstitute.org/blog/?p=187 Thoughts on programming Thu, 29 Jul 2010 21:19:43 -0400 hourly 1 http://wordpress.org/?v=3.0.1 By: yurik http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-1815 yurik Wed, 03 Feb 2010 07:25:32 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-1815 In my honest opinion unit tests are like sandboxes. You can play tiny game in sandbox, than use same code in your short game, than in long game in your terms. But there is no reason to treat all the universe as set of sandboxes, even if it is possible. Looks obvious. But from the perspective of team leader it is really hard to say if other programmers unit tests were necessary or not. Does he really need that many or just spend his time to nothing? Can we trust the code or we need more tests? As for code we have some methods for review, but tests depends on programmer. Programmer keep his eyes open. Or do not keep. He may make tiny steps or big steps. Ok, I see - something is wrong about this programmers test, they take too much time and i see no benefits from this test and that, this one is good, this seems to be useless again. So i need to do smthing more than "Hey, look! This is bad." - "Yep" - "But that is good!" - "Yep" Pair programming looks like good solution but we have only 3 programmers and more than 10 projects (not very valuable but long). In my honest opinion unit tests are like sandboxes. You can play tiny game in sandbox, than use same code in your short game, than in long game in your terms. But there is no reason to treat all the universe as set of sandboxes, even if it is possible. Looks obvious. But from the perspective of team leader it is really hard to say if other programmers unit tests were necessary or not.
Does he really need that many or just spend his time to nothing? Can we trust the code or we need more tests?

As for code we have some methods for review, but tests depends on programmer. Programmer keep his eyes open. Or do not keep. He may make tiny steps or big steps. Ok, I see – something is wrong about this programmers test, they take too much time and i see no benefits from this test and that, this one is good, this seems to be useless again.
So i need to do smthing more than “Hey, look! This is bad.” – “Yep” – “But that is good!” – “Yep”
Pair programming looks like good solution but we have only 3 programmers and more than 10 projects (not very valuable but long).

]]> By: Three Rivers Institute » Blog Archive » To Design or Not To Design? A Third Good Question http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-1198 Three Rivers Institute » Blog Archive » To Design or Not To Design? A Third Good Question Thu, 13 Aug 2009 07:07:36 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-1198 [...] my earlier discussions of testing and defect fixing, I’ll complete the trilogy by discussing the role of design early in [...] [...] my earlier discussions of testing and defect fixing, I’ll complete the trilogy by discussing the role of design early in [...]

]]> By: Three Rivers Institute » Blog Archive » To Fix Or Not To Fix?: Another Good Question http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-1107 Three Rivers Institute » Blog Archive » To Fix Or Not To Fix?: Another Good Question Thu, 06 Aug 2009 14:49:47 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-1107 [...] (This post is the second in a trilogy that started with To Test Or Not To Test?) [...] [...] (This post is the second in a trilogy that started with To Test Or Not To Test?) [...]

]]> By: KentBeck http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-1080 KentBeck Thu, 30 Jul 2009 13:43:50 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-1080 Vivid metaphor, but I don't think we disagree. Testing that accelerates feedback is great on the runway. Expensive testing that trades slower feedback for long-term sustainability is wasteful on the runway. Vivid metaphor, but I don’t think we disagree. Testing that accelerates feedback is great on the runway. Expensive testing that trades slower feedback for long-term sustainability is wasteful on the runway.

]]> By: Jim http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-1079 Jim Thu, 30 Jul 2009 07:59:47 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-1079 Not testing (at the very least the very meaty parts of) a small hobby app is like playing Russian Roulette with your 4 year old daughter, your cat, and Hitler. The odds are not in your favor. Not testing (at the very least the very meaty parts of) a small hobby app is like playing Russian Roulette with your 4 year old daughter, your cat, and Hitler. The odds are not in your favor.

]]> By: Coding: Quick feedback at Mark Needham http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-1010 Coding: Quick feedback at Mark Needham Mon, 20 Jul 2009 11:11:10 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-1010 [...] Beck recently wrote about the trade off between the amount of time it takes to write an automated test and the feedback it gives y... giving an example when developing JUnit Max of a time when his feedback cycle was quicker by not [...] [...] Beck recently wrote about the trade off between the amount of time it takes to write an automated test and the feedback it gives y… giving an example when developing JUnit Max of a time when his feedback cycle was quicker by not [...]

]]> By: Johnny 99 « Grumpy Old Programmer http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-824 Johnny 99 « Grumpy Old Programmer Fri, 03 Jul 2009 11:21:00 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-824 [...] not that code without tests is necessarily bad. I mean, heck, even Kent Beck sometimes flies without a safety net. If it’s write-once-and-throw-away code, then there’s an argument for just getting it [...] [...] not that code without tests is necessarily bad. I mean, heck, even Kent Beck sometimes flies without a safety net. If it’s write-once-and-throw-away code, then there’s an argument for just getting it [...]

]]> By: ADSystems – Agile Development Blog » Kent Beck Sugere Pular os Testes em Projetos de Curto Prazo http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-823 ADSystems – Agile Development Blog » Kent Beck Sugere Pular os Testes em Projetos de Curto Prazo Thu, 02 Jul 2009 22:40:52 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-823 [...] Kent Beck , autor de “ Extreme Programming Explained” e “ Test Driven Development: By Example” sugere que um projeto de software, assim como golf, pode ser um jogo longo ou curto. JUnit é um exemplo de projeto longo, muitos usuários, rentabilidade estável (a $0 é triste para qualquer envolvido), onde o objetivo principal é proporcionar funcionalidades além das necessidades dos usuários. [...] [...] Kent Beck , autor de “ Extreme Programming Explained” e “ Test Driven Development: By Example” sugere que um projeto de software, assim como golf, pode ser um jogo longo ou curto. JUnit é um exemplo de projeto longo, muitos usuários, rentabilidade estável (a $0 é triste para qualquer envolvido), onde o objetivo principal é proporcionar funcionalidades além das necessidades dos usuários. [...]

]]> By: The Real Adam › When to do test-driven development http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-784 The Real Adam › When to do test-driven development Tue, 30 Jun 2009 01:55:04 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-784 [...] earliest stage is proving the idea. He later asserted that when you’re doing stuff like this, you can drop TDD, temporarily. I thought about this and it clicked. If you’re working on a prototype, where [...] [...] earliest stage is proving the idea. He later asserted that when you’re doing stuff like this, you can drop TDD, temporarily. I thought about this and it clicked. If you’re working on a prototype, where [...]

]]> By: JUnit Max » Blog Archive » Developing for the Flight of the Startup http://www.threeriversinstitute.org/blog/?p=187&cpage=1#comment-767 JUnit Max » Blog Archive » Developing for the Flight of the Startup Thu, 25 Jun 2009 21:38:29 +0000 http://www.threeriversinstitute.org/blog/?p=187#comment-767 [...] topic that stimulated this whole line of thinking for me was the question of automated testing. I blogged about how some tests didn’t meet business needs in the takeoff phase. Much sound-biting [...] [...] topic that stimulated this whole line of thinking for me was the question of automated testing. I blogged about how some tests didn’t meet business needs in the takeoff phase. Much sound-biting [...]

]]>