Comments on: Episode 167: The History of JUnit and the Future of Testing with Kent Beck http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/ The Podcast for Professional Software Developers Tue, 14 May 2013 01:48:59 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Software Testing http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-1634 Software Testing Fri, 07 Sep 2012 19:17:12 +0000 http://www.se-radio.net/?p=762#comment-1634 Thank you a lot for such really valuable information found in the your blog. You can get info on Web Application Testing as well with some guidelines with different way of thinking.

]]> By: TDD Cheat Sheet | Fragmented Thoughts http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-1245 TDD Cheat Sheet | Fragmented Thoughts Sun, 04 Dec 2011 00:22:56 +0000 http://www.se-radio.net/?p=762#comment-1245 [...] by staying focused on the software being written. As an aside Software Engineering Radio did an interview with Kent in 2010,  the interview is well worth listening to if you want to get a sense of Kent’s [...]

]]> By: Skilldrick » Podcasts I listen to http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-1107 Skilldrick » Podcasts I listen to Sat, 13 Aug 2011 16:42:59 +0000 http://www.se-radio.net/?p=762#comment-1107 [...] #167: The History of JUnit and the Future of Testing with Kent Beck – it was nice to hear on this episode that even Kent Beck doesn’t test drive when he’s doing highly exploratory work. [...]

]]> By: July 2011 Podcasts for Web Developers, Programmers and Software Engineers | explosive web programming w/ j_blotus http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-1081 July 2011 Podcasts for Web Developers, Programmers and Software Engineers | explosive web programming w/ j_blotus Thu, 21 Jul 2011 15:44:05 +0000 http://www.se-radio.net/?p=762#comment-1081 [...] Shows include: Game Development with Andrew Brownsword (Electronic Arts), The History of JUnit and the Future of Testing with Kent Beck, Rich Hickey on Clojure, and my favorite, Software Craftsmanship with Bob Martin. Check the site [...]

]]> By: The History of JUnit and the Future of Testing with Kent Beck | Software Testing Magazine http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-950 The History of JUnit and the Future of Testing with Kent Beck | Software Testing Magazine Fri, 01 Apr 2011 13:42:49 +0000 http://www.se-radio.net/?p=762#comment-950 [...] In the episode 167 of the Software Engineering Radio, Kent Beck discusses about this tiny little thing he created many years ago and that has changed the daily work of many many programmers in the world: automated unit testing and JUnit. [...]

]]> By: Pratik Pasta Tarifi http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-873 Pratik Pasta Tarifi Tue, 11 Jan 2011 21:19:09 +0000 http://www.se-radio.net/?p=762#comment-873 Very interesting podcast for a young developer like me. thank good pratik pasta tarifi

]]> By: Two podcasts about unit testing | drorhelper http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-811 Two podcasts about unit testing | drorhelper Mon, 06 Dec 2010 07:30:29 +0000 http://www.se-radio.net/?p=762#comment-811 [...] Software Engineering Radio: Episode 167: The History of JUnit and the Future of Testing with Kent Beck [...]

]]> By: Johannes Perlet http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-810 Johannes Perlet Sun, 05 Dec 2010 17:41:17 +0000 http://www.se-radio.net/?p=762#comment-810 Very interesting podcast for a young developer like me. Often I’m confronted with smaller development tasks where I’m not really sure how to solve them and work more exploratory. I got my confirmation that writing tests in that case isn’t necessary if there is not clear whether to use it in further development. Thanks Mr. Beck and SE-Radio.
Johannes

]]> By: John Leger http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-795 John Leger Fri, 12 Nov 2010 13:30:21 +0000 http://www.se-radio.net/?p=762#comment-795 Great episode. Unexpected bonus hearing Kent Beck use Goldie locks and the three bears as a metaphor for when too many tests are involved. I am looking forward to a discussion on Continuous Deployment. I agree with this being a large topic for future concerns and knowledge. TDD adoption is social and there still exists a mire of fear behind its adoption. Fear of the unknown. Every professional who epitomizes their contribution to the craftsmanship of creating software needs to listen to this podcast. Thanks host and Beck for this talk!

John

]]> By: Software Engineering Radio Interview with Kent Beck | Evil Genius Chronicles http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-765 Software Engineering Radio Interview with Kent Beck | Evil Genius Chronicles Tue, 02 Nov 2010 11:58:06 +0000 http://www.se-radio.net/?p=762#comment-765 [...] and try a few episodes out. I just did that with Software Engineering Radio, mainly to hear this interview with Kent Beck. He is the person behind JUnit. In my job I try to to test driven development wherever possible [...]

]]> By: Martin Lippert http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-732 Martin Lippert Wed, 06 Oct 2010 18:53:00 +0000 http://www.se-radio.net/?p=762#comment-732 I don’t know what the common consensus on that problem is. My experience is: if you really do test-driven development, the test coverage of your code must be quite high (because you implement code to get the test green). If there is no test failing, you don’t work on the production code… :-)

Having test coverage as a metric without any real meaning doesn’t make much sense to me. Doing test-driven development to automatically get a high test coverage makes a lot of sense to me.

]]> By: Martin Lippert http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-731 Martin Lippert Wed, 06 Oct 2010 18:49:51 +0000 http://www.se-radio.net/?p=762#comment-731 Hey Matt,

I know such situations from practice. And I know that some people tend to comment out the test, if they are under time pressure. But my observation is that this is often not the real problem. Many times its just a symptom of another, often bigger problem: the team is not test-driven and hasn’t an appropriate Definition-of-Done that includes tests. Skipping tests under time pressure demonstrates that tests aren’t an integral part of programming for them. And skipping tests produces technical debt, from my experience. You can do that, but you loose the value that test produced in the past. And you create a little time bomb for the team… If I need to create that technical debt for whatever reason or pressure, I would hurry to fix that before implementing the next feature.

Just my 2 cents,
Martin

]]> By: Marco Emrich http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-730 Marco Emrich Wed, 06 Oct 2010 15:12:28 +0000 http://www.se-radio.net/?p=762#comment-730 Looks fine in Firefox under Linux too!

]]> By: matt dawson http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-722 matt dawson Sat, 02 Oct 2010 13:01:39 +0000 http://www.se-radio.net/?p=762#comment-722 At one point in the interview the question came up of why teams have tests they don’t run and/or tests that are permanently broken. This seemed like a complete mystery to Martin and Kent.

This issue comes up all the time in practice especially when your tests are not beautifully designed. You have some big complicated test that is failing after some refactor. In all probability the problem is with the test not the code under test. You are under deadline pressure. You have other feedback that tells you everything is working. Do you stop and spend two days debugging the test or do you just comment out the test?

]]> By: Дайджест недели, 1 октября - shlema - блог разработчиков http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-721 Дайджест недели, 1 октября - shlema - блог разработчиков Fri, 01 Oct 2010 11:20:45 +0000 http://www.se-radio.net/?p=762#comment-721 [...] Кент Бек (Kent Beck) рассказывает об истории JUnit и будущем тестирования (подкаст); [...]

]]> By: Písanie testov nespôsobí výbuch hlavy http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-716 Písanie testov nespôsobí výbuch hlavy Wed, 29 Sep 2010 05:58:48 +0000 http://www.se-radio.net/?p=762#comment-716 [...] Vynikajúci rozhovor s Kentom Beckom nájdete na stránkach SE-Radio.net. [...]

]]> By: Jens Schauder http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-715 Jens Schauder Tue, 28 Sep 2010 20:39:15 +0000 http://www.se-radio.net/?p=762#comment-715 If you are interested in the ‘rules’ feature mentioned in the interview you might be interested in these blog posts. (Obviously this is self marketing, but hopefully of the useful kind):

http://blog.schauderhaft.de/2010/08/15/use-cases-for-junit-rules/

http://blog.schauderhaft.de/2009/10/04/junit-rules/

]]> By: marhe http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-713 marhe Mon, 27 Sep 2010 20:25:23 +0000 http://www.se-radio.net/?p=762#comment-713 I missed a topic in your podcast: test coverage tools like clover (every source line has to be tested at least once). I’ve worked in a project where this was an dogmatic issue. My feelings were, that we wasted a lot of time on trivialities. Is there a golden mean, a common consensus on that problem?

]]> By: Martin Lippert http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-710 Martin Lippert Mon, 27 Sep 2010 13:14:11 +0000 http://www.se-radio.net/?p=762#comment-710 Looks fine if I open it in Firefox on Windows and Mac. What version and OS are you using?

]]> By: Bubba http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-709 Bubba Mon, 27 Sep 2010 12:57:52 +0000 http://www.se-radio.net/?p=762#comment-709 Your site is totally unreadable in Firefox. OK in Chrome.

]]> By: Tweets that mention Episode 167: The History of JUnit and the Future of Testing with Kent Beck | Software Engineering Radio -- Topsy.com http://www.se-radio.net/2010/09/episode-167-the-history-of-junit-and-the-future-of-testing-with-kent-beck/#comment-701 Tweets that mention Episode 167: The History of JUnit and the Future of Testing with Kent Beck | Software Engineering Radio -- Topsy.com Sun, 26 Sep 2010 21:16:40 +0000 http://www.se-radio.net/?p=762#comment-701 [...] This post was mentioned on Twitter by Kent Beck, Michael Easter, Sebastian Sanitz, Martin Lippert, Martin Lippert and others. Martin Lippert said: RT @seradio: New episode: Episode 167: The History of JUnit and the Future of Testing with Kent Beck http://bit.ly/aQvkBu [...]

]]>