Comments on: The Fuzz on Developer Testing http://thediscoblog.com/2006/02/07/developer-testing-defined/ Can you dig it man? Tue, 07 Oct 2008 13:55:04 +0000 http://wordpress.org/?v=2.6 By: Michael http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-2020 Michael Wed, 22 Nov 2006 05:39:22 +0000 http://thediscoblog.com/?p=5#comment-2020 <strong>Yep...</strong> Weird enough for government work. ... Yep…

Weird enough for government work.
…

]]> By: Test Early » Functional tests à la Selenium http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-1054 Test Early » Functional tests à la Selenium Tue, 08 Aug 2006 01:47:52 +0000 http://thediscoblog.com/?p=5#comment-1054 [...] I’ve written about three test categories (unit, component and system) for developer testing on a number of occasions- and I’ve even tried to draw a distinction between system functional tests. Briefly, a system test verifies a software application from system end points, like web pages or web services- but they mimic the user or the end point protocol. [...] [...] I’ve written about three test categories (unit, component and system) for developer testing on a number of occasions- and I’ve even tried to draw a distinction between system functional tests. Briefly, a system test verifies a software application from system end points, like web pages or web services- but they mimic the user or the end point protocol. [...]

]]> By: The Disco Blog » Adventures in NUnit test categorization http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-413 The Disco Blog » Adventures in NUnit test categorization Fri, 09 Jun 2006 14:20:24 +0000 http://thediscoblog.com/?p=5#comment-413 [...] As new tests are added to a code base, the build time will invariably increase. As I have written about before, a process of copasetic test categorization can be employed to help manage build times and thus, test frequencies. As it turns out, test categorization is easy to implement in NUnit using the aptly named Category attribute. [...] [...] As new tests are added to a code base, the build time will invariably increase. As I have written about before, a process of copasetic test categorization can be employed to help manage build times and thus, test frequencies. As it turns out, test categorization is easy to implement in NUnit using the aptly named Category attribute. [...]

]]> By: The Disco Blog » Hip system tests with Cargo http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-53 The Disco Blog » Hip system tests with Cargo Sat, 22 Apr 2006 02:04:18 +0000 http://thediscoblog.com/?p=5#comment-53 [...] System tests require a fully installed system up and running to execute properly. In web environments, this presents an interesting challenge- a servlet container needs to up running with the latest and greatest code before any copasetic tests can be run. [...] [...] System tests require a fully installed system up and running to execute properly. In web environments, this presents an interesting challenge- a servlet container needs to up running with the latest and greatest code before any copasetic tests can be run. [...]

]]> By: The Disco Blog » It’s all about test categorization, man http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-15 The Disco Blog » It’s all about test categorization, man Fri, 17 Feb 2006 03:22:21 +0000 http://thediscoblog.com/?p=5#comment-15 [...] A true unit test should run to completion (successfully) in less than a few seconds. If a unit test takes longer, take a close look at it- it is either broken or really a component level test. Because unit tests run so quickly, they should be run anytime a build is run. [...] [...] A true unit test should run to completion (successfully) in less than a few seconds. If a unit test takes longer, take a close look at it- it is either broken or really a component level test. Because unit tests run so quickly, they should be run anytime a build is run. [...]

]]> By: The Disco Blog » Reliability’s Skinney http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-8 The Disco Blog » Reliability’s Skinney Fri, 10 Feb 2006 03:12:12 +0000 http://thediscoblog.com/?p=5#comment-8 [...] Bottom line: if we are to build software systems which are truly reliable, we have to ensure reliability at the object level, which can only be achieved through unit testing. Otherwise, we can’t possibly hope to build highly reliable applications. [...] [...] Bottom line: if we are to build software systems which are truly reliable, we have to ensure reliability at the object level, which can only be achieved through unit testing. Otherwise, we can’t possibly hope to build highly reliable applications. [...]

]]> By: Rob Sanheim http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-7 Rob Sanheim Wed, 08 Feb 2006 19:10:27 +0000 http://thediscoblog.com/?p=5#comment-7 JUnit can be used for all sorts of developer tests, its not limited to unit tests, despite the name. TestNG may be better suited to some styles of higher level tests (ie order-dependant tests), but don't think the "jUnit" == unit test only. JUnit can be used for all sorts of developer tests, its not limited to unit tests, despite the name. TestNG may be better suited to some styles of higher level tests (ie order-dependant tests), but don’t think the “jUnit” == unit test only.

]]> By: Andy http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-6 Andy Wed, 08 Feb 2006 15:54:39 +0000 http://thediscoblog.com/?p=5#comment-6 Indeed, TestNG is an excellent framework for non unit testing. I agree 100%- I plan on doing another article on the benefits of TestNG. In the mean time, check out a <a href="http://www.vanwardtechnologies.com/nfjs/testng/testng.pdf">presentation</a> I've done on TestNG. Indeed, TestNG is an excellent framework for non unit testing. I agree 100%- I plan on doing another article on the benefits of TestNG. In the mean time, check out a presentation I’ve done on TestNG.

]]> By: x http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-5 x Wed, 08 Feb 2006 15:07:09 +0000 http://thediscoblog.com/?p=5#comment-5 JUnit is for unit testing only. For the non-unit tests that you show, you should be using <a href="http://testng.org">TestNG </a>. JUnit is for unit testing only. For the non-unit tests that you show, you should be using TestNG .

]]> By: Mikael Gueck http://thediscoblog.com/2006/02/07/developer-testing-defined/#comment-4 Mikael Gueck Wed, 08 Feb 2006 14:35:30 +0000 http://thediscoblog.com/?p=5#comment-4 And here I was hoping to see you interview your local Police Department about developer testing. And here I was hoping to see you interview your local Police Department about developer testing.

]]>