[jboss-dev-forums] [QA of JBoss Portal] - Re: JBoss Unit design (ant and maven support)

[julien@jboss.com]

I ended up introducing a TestRunnerContext instead of the TestFilter for running tests:


  | public interface TestRunnerContext
  | {
  |    TestFilter getFilter();
  |    Map<String,String> getProperties();
  | }
  | 

Properties are propagated to test drivers so they can use it for configuration during the life cycle phase I introduced (which is a good idea imho).

I plan to move runner listener support to TestRunnerContext instead of making it part of the TestRunner interface, so basically remove the add/remove listener and rather have a fireEvent(TestRunnerEvent) on the TestRunnerContext which will provide more flexiblity.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094559#4094559

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094559