Simple-method-test-suite

[Scott Gray-2]

Hi All,

In a test def I would like to be able to specify a entire file of  
simple-method tests where every simple method in the file would be run  
in succession similar to how junit-test-suite works where every method  
in a class is run as a test.

The way I see it there are two options:
1.  Remove the requirement that the simple-method-test element must  
provide a simple method name to run.  If it is omitted then then every  
simple method should be run.
2.  Add a new element simple-method-test-suite specifically for this  
purpose.

The goal here is to make tests a little easier to write.

Thanks
Scott

HotWax Media
http://www.hotwaxmedia.com

[Ashish Vijaywargiya-5]

Please see my comments inline:

Scott Gray wrote:

> Hi All,
>
> In a test def I would like to be able to specify a entire file of
> simple-method tests where every simple method in the file would be run
> in succession similar to how junit-test-suite works where every method
> in a class is run as a test.
>
> The way I see it there are two options:
> 1.  Remove the requirement that the simple-method-test element must
> provide a simple method name to run.  If it is omitted then then every
> simple method should be run.

Instead of adding new element I will prefer to update the code to handle

the case of keeping simple method name optional.
Like if we don't have simple method name then run all the simple methods
present in a file and if we have simple method name then run only that one.

WDYT ?

--
Ashish

> 2.  Add a new element simple-method-test-suite specifically for this
> purpose.
>
> The goal here is to make tests a little easier to write.
>
> Thanks
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
>
>

[Scott Gray-2]

Yeah I think that's the best option too, I'll make sure it's  
documented in the xsd so the behavior is clear.  Thanks Ashish.

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 2/05/2009, at 7:06 PM, Ashish Vijaywargiya wrote:

> Please see my comments inline:
>
> Scott Gray wrote:
>> Hi All,
>>
>> In a test def I would like to be able to specify a entire file of  
>> simple-method tests where every simple method in the file would be  
>> run in succession similar to how junit-test-suite works where every  
>> method in a class is run as a test.
>>
>> The way I see it there are two options:
>> 1.  Remove the requirement that the simple-method-test element must  
>> provide a simple method name to run.  If it is omitted then then  
>> every simple method should be run.
> Instead of adding new element I will prefer to update the code to  
> handle the case of keeping simple method name optional.
> Like if we don't have simple method name then run all the simple  
> methods present in a file and if we have simple method name then run  
> only that one.
>
> WDYT ?
>
> --
> Ashish
>> 2.  Add a new element simple-method-test-suite specifically for  
>> this purpose.
>>
>> The goal here is to make tests a little easier to write.
>>
>> Thanks
>> Scott
>>
>> HotWax Media
>> http://www.hotwaxmedia.com
>>
>>
>>

[Ashish Vijaywargiya-5]

Your most welcome, Scott :-) !

--
Ashish

Scott Gray wrote:

> Yeah I think that's the best option too, I'll make sure it's
> documented in the xsd so the behavior is clear.  Thanks Ashish.
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 2/05/2009, at 7:06 PM, Ashish Vijaywargiya wrote:
>
>

[David E Jones-3]

On May 2, 2009, at 1:06 AM, Ashish Vijaywargiya wrote:

> Please see my comments inline:
>
> Scott Gray wrote:
>> Hi All,
>>
>> In a test def I would like to be able to specify a entire file of  
>> simple-method tests where every simple method in the file would be  
>> run in succession similar to how junit-test-suite works where every  
>> method in a class is run as a test.
>>
>> The way I see it there are two options:
>> 1.  Remove the requirement that the simple-method-test element must  
>> provide a simple method name to run.  If it is omitted then then  
>> every simple method should be run.
> Instead of adding new element I will prefer to update the code to  
> handle the case of keeping simple method name optional.
> Like if we don't have simple method name then run all the simple  
> methods present in a file and if we have simple method name then run  
> only that one.

I agree, that sounds line a much better option and is pretty intuitive  
(ie it makes sense it would work that way).

-David

>> 2.  Add a new element simple-method-test-suite specifically for  
>> this purpose.
>>
>> The goal here is to make tests a little easier to write.
>>
>> Thanks
>> Scott
>>
>> HotWax Media
>> http://www.hotwaxmedia.com
>>
>>
>>