Comments on: How to Unit-test private methods http://technology.amis.nl/2007/09/24/how-to-unit-test-private-methods/?utm_source=rss&utm_medium=rss&utm_campaign=how-to-unit-test-private-methods Fri, 12 Apr 2013 10:04:09 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Tom http://technology.amis.nl/2007/09/24/how-to-unit-test-private-methods/#comment-4915 Tom Sun, 02 Aug 2009 08:17:42 +0000 http://technology.amis.nl/blog/?p=2411#comment-4915 A private method call generator: http://code.google.com/p/hexacta-booster/
Enjoy!

]]> By: Peter Lawrey http://technology.amis.nl/2007/09/24/how-to-unit-test-private-methods/#comment-4914 Peter Lawrey Tue, 25 Sep 2007 20:35:14 +0000 http://technology.amis.nl/blog/?p=2411#comment-4914 You can access private method this way, but you shouldn’t need to unit test them. They should be hidden implementation details which you should be able to replace or remove without breaking your unit tests.
If you really must test them, you can make them package private and give your unit tests the same package. (in another base directory)

You can do alot worse with reflections. You can set final fields and static finals. You can get the “defineClass” method on your class loader and inject classes which don’t appear on disk.
If you want really dangerous, try the sun.misc.Unsafe class which lets you do alot of the things Java was supposed to prevent you from doing. :)

]]>