Mark, Thank you for catching my mistake. I've added XMLUITestRunner to the patch, it's updated in jira or you can download it here:
http://scott.phillips.name/wp-content/uploads/2010/04/Dspace-1.5.2-FunctionalTest-V2.patch.txt Scott-- On Apr 7, 2010, at 5:58 PM, Mark Diggory wrote: > I know its in Elliot's SVN and listed in the Community section of > the wiki.... > http://wiki.dspace.org/confluence/display/DSPACE/Emetsger__15xFeatureBranches > > Unit Testing > • Includes dependencies, Maven 2 project structure, and test > harness for unit testing. Most (if not all) feature branches have > this branch already merged in. > • Unit Testing Branch > • Mock Library and Test Harness > • Resources for Mock library (dspace.cfg, log4j.properties, etc) > > And in response to Scott... I'm not rejecting the proposal... just > evaluating it... I think we should move forward with the applying of > the work simply because of your effort up to this point is vetted in > a deployed scenario, well written and generally stable. > > 1.) We need to be clear about separating Unit Testing the codebase > from kicking the tires of an installation. So, I rather like your > separation for the test classes into a separate module. we do still > need to think about true Unit testing and it should remain separate > so please scratch my idea about using src/test/java. > > 2.) We need to get the modules properly broken up and out from the > synchronous release cycle like we discussed previously in our IRC > meetings. This means moving more of the dspace-xxx code into the > modules space and organizing accordingly. > > 3.) So a Testing Harness, even if called from Ant should be a > separate project that can be called independently against any DSpace > URL and I think you are getting us a good start here. > > 4.) However, work like dspace-discovery will completely violate > these test classes as they replace significant Search and Browse > logic. > > 5.) Finally, Scott, I think your missing a class in your patch... > org.dspace.app.xmlui.XMLUITestRunner > > Mark > > > > On Wed, Apr 7, 2010 at 7:24 AM, Tim Donohue <tdono...@duraspace.org> > wrote: > > > > On 4/6/2010 11:50 AM, Mark Diggory wrote: > > > >> We also have considerations in that we have a great body of work in > >> Elliot Metsgers Mock DSpace object and JUint testing framework,. > > > > Mark or Elliot (if you are listening in), > > > > This begs the question -- do we have Elliot's past work in our SVN > > somewhere? I took a quick glance around and didn't see it. > Might be good > > to get all of this somewhere in SVN & Jira, so that we can start > to move > > forward on one or more of these testing frameworks (or merge code as > > needed). > > > > - Tim > > > > > > -- > Mark R. Diggory > Head of U.S. Operations - @mire > > http://www.atmire.com - Institutional Repository Solutions > http://www.togather.eu - Before getting together, get t...@ther > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev_______________________________________________ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
