Comments on: How to customize your jUnit Behavior and Interaction http://www.beilers.com/2009/05/how-to-customize-your-junit-behavior-and-interaction/?utm_source=rss&utm_medium=rss&utm_campaign=how-to-customize-your-junit-behavior-and-interaction Crazy Thoughts on Software Development and Life in General Sat, 07 Jan 2012 03:56:19 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Sam Brannen http://www.beilers.com/2009/05/how-to-customize-your-junit-behavior-and-interaction/#comment-31 Sam Brannen Wed, 20 May 2009 20:37:08 +0000 http://www.beilers.com/?p=387#comment-31 Hi Phil, First and foremost, I'm glad to see you're finding ways to extend the Spring TestContext Framework for your own custom needs! Secondly, you can simplify your solution: 1) Create your own TestExecutionListener (TEL) which extends AbstractTestExecutionListener and overrides prepareTestInstance(). 2) Your custom TEL can access the annotations present on the test class via testContext.getTestClass() (i.e., the code in your AuthorizedSpringjUnit4ClassRunner should logically be in your custom TEL). Note that the TestContext is passed to each method of a TEL. 3) Configure your test class with both your custom TEL and DependencyInjectionTestExecutionListener (DITEL), but make sure to include your custom TEL before DITEL in @TestExecutionListeners. In other words, there is no need to extend DependencyInjectionTestExecutionListener. Similarly, there is rarely a need to extend SpringJUnit4ClassRunner, since the TestExecutionListener infrastructure generally provides all the hooks you need. Hope this helps. Regards, Sam Hi Phil,

First and foremost, I’m glad to see you’re finding ways to extend the Spring TestContext Framework for your own custom needs!

Secondly, you can simplify your solution:

1) Create your own TestExecutionListener (TEL) which extends AbstractTestExecutionListener and overrides prepareTestInstance().

2) Your custom TEL can access the annotations present on the test class via testContext.getTestClass() (i.e., the code in your AuthorizedSpringjUnit4ClassRunner should logically be in your custom TEL). Note that the TestContext is passed to each method of a TEL.

3) Configure your test class with both your custom TEL and DependencyInjectionTestExecutionListener (DITEL), but make sure to include your custom TEL before DITEL in @TestExecutionListeners.

In other words, there is no need to extend DependencyInjectionTestExecutionListener. Similarly, there is rarely a need to extend SpringJUnit4ClassRunner, since the TestExecutionListener infrastructure generally provides all the hooks you need.

Hope this helps.

Regards,

Sam

]]>