Patch for running RunSuite with a list of suites (was Re: !$!% derbyall)

["David W. Van Couvering" <Da...@Sun.COM>]

This is great, Andrew, thanks!

Can anyone tell me how I find out, if derbyall or any suite goes down 
half-way through, what suites have run so far, and which ones have 
passed and which ones have failed?

Thanks,

David

Andrew McIntyre wrote:
> On 4/12/06, Andrew McIntyre <mc...@gmail.com> wrote:
> 
>>On 4/12/06, David W. Van Couvering <Da...@sun.com> wrote:
>>
>>><rant on>
>>>Sorry, but it is so frustrating.  I started a derbyall run at 9 this
>>>morning, and it was still running this evening.  My CPU was at 100%, I
>>>could get barely any work done, and then my machine hung up, I had to
>>>reboot, and the way our harness works you have to start *completely from
>>>scratch* -- there is no way to start from the beginning.
>>></rant off>
>>
>>I'm with you on that. I've always wanted to have RunSuite take a list
>>of suites, not just one.
> 
> 
> Rant and you shall recieve? Attached is a patch which does the above.
> It turned out to be a little more difficult than I thought, because
> the harness actually does some setup in getSuiteProperties (bad
> harness! bad!), so I couldn't just override the value of the suites
> field. But then again turned out to not be so bad, since
> getSuiteProperties already included functionality to load a suite
> definition from the current directory, so I just needed to write out a
> new adhoc suite definition.
> 
> In other news, RunSuite can read a suite definition from the current
> directory. Did anyone else know that? I didn't. Anyway, makes this
> patch sort of moot. But with the patch its even more direct, just
> enter the suites you want to run on the command line.
> 
> cheers,
> andrew

Re: Patch for running RunSuite with a list of suites (was Re: !$!% derbyall)

[Andrew McIntyre <mc...@gmail.com>]

On 4/13/06, David W. Van Couvering <Da...@sun.com> wrote:
> Great, thanks.
>
> I'll try your patch out.  Is this something you'll commit if it works
> for you (and me)?

Sure. I think I'd rather call the new method adhocSuite instead of
overrideSuites, since that's more descriptive, and I've some other
minor mods to make before it goes in, but if it works out for you,
I'll commit.

andrew

Re: Patch for running RunSuite with a list of suites (was Re: !$!% derbyall)

["David W. Van Couvering" <Da...@Sun.COM>]

Great, thanks.

I'll try your patch out.  Is this something you'll commit if it works 
for you (and me)?

David

Andrew McIntyre wrote:
> On 4/13/06, David W. Van Couvering <Da...@sun.com> wrote:
> 
>>Can anyone tell me how I find out, if derbyall or any suite goes down
>>half-way through, what suites have run so far, and which ones have
>>passed and which ones have failed?
> 
> 
> In the directory where you were running the tests will be a file
> {suite}.sum, which contains a running list of all the tests that had
> run so far. you'll need to take a look at the order of the suites in
> derbyall to determine where you were, exactly. But just search for
> 'Failed' in the sum file and you'll find the diff of any failures that
> had already occurred.
> 
> andrew

Re: Patch for running RunSuite with a list of suites (was Re: !$!% derbyall)

[Andrew McIntyre <mc...@gmail.com>]

On 4/13/06, David W. Van Couvering <Da...@sun.com> wrote:
>
> Can anyone tell me how I find out, if derbyall or any suite goes down
> half-way through, what suites have run so far, and which ones have
> passed and which ones have failed?

In the directory where you were running the tests will be a file
{suite}.sum, which contains a running list of all the tests that had
run so far. you'll need to take a look at the order of the suites in
derbyall to determine where you were, exactly. But just search for
'Failed' in the sum file and you'll find the diff of any failures that
had already occurred.

andrew