Comments on: How to Write Good Unit Tests http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests Wed, 08 Feb 2012 03:57:22 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Basil Vandegriend http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-133114 Basil Vandegriend Mon, 27 Jun 2011 03:43:12 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-133114 @Shashhank, there are many options for testing database interactions. If you need to do lots of data setup, I suggest checking out DBUnit. My preferred approach, assuming you are using Spring for transaction management, is to use Spring's test framework so that each test involving the database executes as a single transaction that is rolled back, thus minimizing the problems from having tests change data in the database. @Shashhank, there are many options for testing database interactions. If you need to do lots of data setup, I suggest checking out DBUnit. My preferred approach, assuming you are using Spring for transaction management, is to use Spring’s test framework so that each test involving the database executes as a single transaction that is rolled back, thus minimizing the problems from having tests change data in the database.

]]> By: Shashank http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-133063 Shashank Sun, 26 Jun 2011 08:09:59 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-133063 Basil, I am looking for guidance on writing a test suite for set of java files doing either persistance of xml to DB or doing manipulation, validation of Data in DB. any references doing the same would be of great help. Thanks. Basil, I am looking for guidance on writing a test suite for set of java files doing either persistance of xml to DB or doing manipulation, validation of Data in DB. any references doing the same would be of great help.

Thanks.

]]> By: Aleksei http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-118752 Aleksei Wed, 05 Jan 2011 18:49:08 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-118752 In fact, quite unuseful article... Most of thing are too obvious but the principles of designing test cases are not covered. In fact, quite unuseful article… Most of thing are too obvious but the principles of designing test cases are not covered.

]]> By: Testing / Unit Testing – Session 1 « Allan Waddell’s Weblog http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-113053 Testing / Unit Testing – Session 1 « Allan Waddell’s Weblog Sat, 09 Oct 2010 02:46:06 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-113053 [...] How to write good unit tests: http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests [...] [...] How to write good unit tests: http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests [...]

]]> By: Why is automated unit testing important? « Ryan Eastabrook http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-104354 Why is automated unit testing important? « Ryan Eastabrook Wed, 17 Feb 2010 04:21:18 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-104354 [...] (Java): http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests Categories: Uncategorized Comments (0) Trackbacks (0) Leave a comment [...] [...] (Java): http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests Categories: Uncategorized Comments (0) Trackbacks (0) Leave a comment [...]

]]> By: Basil Vandegriend http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-97714 Basil Vandegriend Sat, 26 Sep 2009 02:36:43 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-97714 @tinca, I often do write tests for a method based on its contract (preconditions & postconditions). However, I seldom test for the negative case (e.g. that the method fails with an exception if a precondition is violated). Instead, I focus on testing that the method behaves properly when the preconditions are met. E.g. if an argument can be null, then I verify that the method accepts a null as well as a non-null value. @tinca, I often do write tests for a method based on its contract (preconditions & postconditions). However, I seldom test for the negative case (e.g. that the method fails with an exception if a precondition is violated). Instead, I focus on testing that the method behaves properly when the preconditions are met. E.g. if an argument can be null, then I verify that the method accepts a null as well as a non-null value.

]]> By: tinca http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-97683 tinca Fri, 25 Sep 2009 05:41:24 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-97683 Would you write cases that test contracts? For instance: when null is passed IllegalArgumentException must be thrown? It may seem a trivial one, but on the long run it can protect again accidental changes. Would you write cases that test contracts? For instance: when null is passed IllegalArgumentException must be thrown? It may seem a trivial one, but on the long run it can protect again accidental changes.

]]> By: Basil Vandegriend http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-79305 Basil Vandegriend Sat, 07 Feb 2009 14:00:42 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-79305 @Rick, there are a few guidelines I can provide about when the code is not trivial. The two solid examples I provided in the article where getter & setter methods with no logic and simple constructors (that just populate fields from parameters passed in). Another example would be delegate methods that simnply delegate execution to another class. I.e. private Bar delegate; public void doStuff(Foo foo) { delegate.doStuff(foo); } The general principle is this: how confident are you that the code is correct? If you are 100% confident, then this is trivial code that you do not need to test. If you have doubts or uncertainties, then you should write a test. @Rick, there are a few guidelines I can provide about when the code is not trivial. The two solid examples I provided in the article where getter & setter methods with no logic and simple constructors (that just populate fields from parameters passed in). Another example would be delegate methods that simnply delegate execution to another class. I.e.
private Bar delegate;

public void doStuff(Foo foo) {
delegate.doStuff(foo);
}

The general principle is this: how confident are you that the code is correct? If you are 100% confident, then this is trivial code that you do not need to test. If you have doubts or uncertainties, then you should write a test.

]]> By: Rick Pingry http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-79107 Rick Pingry Fri, 06 Feb 2009 23:58:14 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-79107 I would like to know more about writing tests for trivial code. When is the code NOT trivial? Where is the line between trivial code and non-trivial code? Can anyone provide some solid examples? I would like to know more about writing tests for trivial code. When is the code NOT trivial? Where is the line between trivial code and non-trivial code? Can anyone provide some solid examples?

]]> By: Basil Vandegriend http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests/comment-page-1#comment-71972 Basil Vandegriend Wed, 07 Jan 2009 01:46:25 +0000 http://www.basilv.com/psd/blog/2006/how-to-write-good-unit-tests#comment-71972 @Deepak, thanks for your comment. The article does provide guidance on how to transform the 'what-not-to-do' examples into better tests. I explicitly wrote the article this way to provide some concrete guidance to people to write better tests, but you are right that I do not provide instructions on the basics of writing a good test case. I am tentatively planning to write some more articles on unit testing in the near future, so stay tuned. @Deepak, thanks for your comment. The article does provide guidance on how to transform the ‘what-not-to-do’ examples into better tests. I explicitly wrote the article this way to provide some concrete guidance to people to write better tests, but you are right that I do not provide instructions on the basics of writing a good test case. I am tentatively planning to write some more articles on unit testing in the near future, so stay tuned.

]]>