You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by ji...@apache.org on 2004/05/28 16:30:01 UTC

[jira] Closed: (JS2-59) Remove test case reliance on pico container/groovy scripts

Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-59

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-59
    Summary: Remove test case reliance on pico container/groovy scripts
       Type: Task

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Jetspeed 2
 Components: 
             Components Core
             Project Build
   Fix Fors:
             2.0-a1

   Assignee: Scott T Weaver
   Reporter: Scott T Weaver

    Created: Thu, 27 May 2004 8:54 AM
    Updated: Fri, 28 May 2004 7:28 AM

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 ;)


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org