[Dev] Re: About options and the JUnit button

[Frank Cohen]

Please use milliseconds for all values.

The JUnit TestCase button should create the attached skeleton.

-Frank

-------------- next part --------------
A non-text attachment was scrubbed...
Name: testcase.py
Type: text/x-python-script
Size: 1444 bytes
Desc: not available
Url : http://cake.pushtotest.com/pipermail/dev/attachments/20070517/5f7b43d7/testcase.bin
-------------- next part --------------

On May 17, 2007, at 10:03 AM, William Mart?nez Pomares wrote:

>
>
>  -----Original Message-----
> From:   Luis Carlos Lara L?pez
> Sent:   Thursday, May 17, 2007 10:32 AM
> To:     William Mart?nez Pomares
> Subject:        to frank
> Importance:     High
>
> Actual state of the times flags
>
> <options>
>                 <sleeptime>0</sleeptime>
>                 <delayBetweenStartingUseCasses time="1000"/>
>                 <delayBetweenTestCases time="100"/>
>                 <testTime time="1000"/>
> </options>
>
>
> I think its better to use the same format. Something like that
>
> <options>
>                 <sleeptime time="0"/>
>                 <delayBetweenStartingUseCasses time="1000"/>
>                 <delayBetweenTestCases time="100"/>
>                 <testTime time="1000"/>
> </options>
>
> Currently all time all in miliseconds, do you like it in seconds?
>
>
>
> In the new scenario screen there is a button name jUnit TestCase.  
> This button currently do nothing. What is the function of this button
>
> (The generic Scalability Test create the test skeleton you give us)
>
>
>



--
Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 374 7426
TestMaker: The open-source SOA test automation tool