Comments for MacBean Technology http://macbeantechnology.co.uk Wed, 12 Jan 2011 10:50:21 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Automate Testing JavaBeans by Andrew Dunnhttp://macbeantechnology.co.uk/blog/automate-testing-javabeans/comment-page-1/#comment-24 Andrew Dunn Wed, 12 Jan 2011 10:50:21 +0000 http://macbeantechnology.co.uk/?p=425#comment-24 Great job, I have on the odd occasion thought about doing something similar. I will disagree slightly with you about the need to test JavaBeans, these should always be tested. Not for the getters and setters explicitly but for the hashcode and equals methods. JavaBeans should always override these methods and these methods are easy to add using eclipse (it's just a right click to generate it).When I say a great start I think that this should be taken further. A couple of enhancements would be to change it so that the hashcode and equals are always tested by default. Secondly it would be really good to test scenarios where hashcode and equals should not be equal, i.e. change the value of each property on one of the beans one at a time and check that the hashcode and equals are different (remembering to change the value back after the test). I have seen many examples where a new property is added onto the bean and the hashcode or equals (if it is actually overridden) has not been updated.But like I said, great job. Great job, I have on the odd occasion thought about doing something similar. I will disagree slightly with you about the need to test JavaBeans, these should always be tested. Not for the getters and setters explicitly but for the hashcode and equals methods. JavaBeans should always override these methods and these methods are easy to add using eclipse (it’s just a right click to generate it).

When I say a great start I think that this should be taken further. A couple of enhancements would be to change it so that the hashcode and equals are always tested by default. Secondly it would be really good to test scenarios where hashcode and equals should not be equal, i.e. change the value of each property on one of the beans one at a time and check that the hashcode and equals are different (remembering to change the value back after the test). I have seen many examples where a new property is added onto the bean and the hashcode or equals (if it is actually overridden) has not been updated.

But like I said, great job.

]]>