[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: WiredMicrocontainerTest

[adrian@jboss.org]

"alesj" wrote : "adrian at jboss.org" wrote : Either add the feature to the MicrocontainerTest class or move it to src/tests
  | I don't want all the tests to be autowired.
  | But on the other hand this is a generic MC test util, so imho it should be where it is.
  | As a user I don't want to pull all the kernel tests just to get what the kernel module is all about, this test. :-)

MicrocontainerTest is the exported test. I don't want lots of different test parents
with the N<->M problem for different features.

I already went through and fixed this once and combined three or four classes
you'd created in the package back into the main test class. :-)
There's a previous thread about it somewhere?

The correct way to do this, if you want subclasses to use it is to allow it to be
enabled with something like:


  | public MyTest(String name)
  | {
  |    super(name);
  |    // or whatever you want to call the property
  |    setRegisterTestInController(true);
  | }
  | 

The same goes for any other features you think are generic enough
to be used elsewhere.


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

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