On 22 Sep 2014, at 17:35, Ben Coman <[email protected]> wrote: > Martin McClure wrote: >> This fix required multiple slices since loading things in the wrong order >> broke exceptions badly enough to hang the system. I packaged things in five >> slices. (It's possible that if Monticello was smart enough I could have done >> it in less than five, but it did need more than one). >> >> The automatic test runner seems to only load the first of the five slices. >> Therefore two exception tests fail, which is expected. All exception tests >> should pass after all five slices are loaded in order. >> >> Is there a way to tell the automatic test runner to load all five, or does >> this one require manual testing? (I did test it manually before dropping the >> slices in the inbox, but that was a month ago.) >> >> Regards, >> >> -Martin >> >> > There is no built in mechanism for loading multiple slices. Now perhaps your > slice can contain only a "Dummy class>>initialize" method that scripts > Gopher to load the slices in order. Disclaimer, never tried it - just > thinking out loud.
I think the easiest is to make sub-cases: then they will be checked with the
leaf first, after it is integrated (and closed), the parent gets tested, and so
on.
Marcus
signature.asc
Description: Message signed with OpenPGP using GPGMail
