Agreed. It'd be great to have tests of the generated assembly and more importantly - test that the examples actually work.
On 7/7/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
Yeah.. I've also felt that if we did have tests in the assembly module, they should be testing things like.. unzip that assembly and verify that the default configuration works in that assembly. Also that the examples work in the assembly. etc. etc. Stuff related to testing the packaging. Perhaps even tests that make sure the we have READMEs and NOTICE files. Regards, Hiram On 7/7/06, James Strachan <[EMAIL PROTECTED]> wrote: > > On 7/7/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: > > Sounds fine to me. > > Its always kinda bugged me that you'd have to wait for an entire > assembly to build to know if you'd broken something in activemq-core > :) > > Plus it was much easier doing this than figuring out why the tests > were not running in the assembly module :) > > > > On 7/7/06, James Strachan <[EMAIL PROTECTED]> wrote: > > > > > > We had a bunch of test cases in the assembly module that were not > > > being executed in the m2 build for some reason; its also for legacy > > > reasons they were there, they are better suited to being closer to the > > > actual code they test so I've just moved them to the activemq-core > > > project. > > > > > > So don't panic if you do a svn update; there's not loads more (slow) > > > tests been added :) they've just been moved about a bit :) > > > > > > -- > > > > > > James > > > ------- > > > http://radio.weblogs.com/0112098/ > > > > > > > > > > > -- > > Regards, > > Hiram > > > > Blog: http://hiramchirino.com > > > > > > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > -- Regards, Hiram Blog: http://hiramchirino.com
-- James ------- http://radio.weblogs.com/0112098/
