[JS2-59] Remove test case reliance on pico container/groovy scripts

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-a1
• Component/s: Components Core, Project Build
• Assignee: Scott Weaver
• Reporter: Scott Weaver
• Created: 27/May/04 15:54
• Updated: 28/May/04 14:28
• Resolved: 28/May/04 14:28

Description

Since we are now assembling our components with out using NanoQuickAssembler, the need for external .groovy assembly scripts have diminished.

I have created 3 base test cases that that provide all the functionality of providing persistence and registry support for all other test cases. I think this MUCH better than trying to manage a myriad of this-container.groovy and test-this-container.groovy, that are starting crop up all over the place like acne on a teenager's face. Again, I take full responsibilltity for this by introducing the NanoQuickAssembler.

This automcatically mitigates the need to have pico containers within our test cases. There is absolutley no need to clutter the test cases with containers, when it is easier to just instantiate those components by hand. We have gotten to this point because of our dilligence toward component oriented development. It is now so easy to know exactly what our components need to be tested (in most cases) just by looking at the constructor signature.

With the new base test case classes in place there will only be one groovy script, jetspeed.groovy. At least for now