[Dev] Function Buttons

[William Martinez Pomares]

Ok.
I don't understand the part about running local. Per TestScenario nodes
description, I can define the remote nodes where to run. 
That means TM will connect to testnetwork testnodes and run the tests
from there. I assume the jars to load and the actual TestScenario.xml is
sent to the testnodes and it will run there. 

When I say running local, I meant to test the TestScenario locally:
uploading the jars and executing the xml. This will not require to send
it to the testnodes, and thus we can run the scenario from testmaker
rather than remotely.

What do you think.
William.

-----Original Message-----
From: dev-bounces at lists.pushtotest.com
[mailto:dev-bounces at lists.pushtotest.com]On Behalf Of Frank Cohen
Sent: Friday, February 23, 2007 2:15 PM
To: TestMaker Developers List
Subject: Re: [Dev] Function Buttons


Good questions. See below.

> 1. We have a Pause button and a Stop button. I can think of a remote
> running test, where a test may take several minutes to complete and I
> left a test scenario running (with several usecases and crlevels).  
> Now,
> I may want to stop the test for something, but I would like the  
> current
> cycle to finish not to lose the actual testing done so far. I may  
> want,
> in the other hand, to stop the test inmediately, since I have an
> emergency. These can be the actual examples for these two cases. Now,
> for pause to actually pause an ongoing cycle? It does not make sense
> since the test would become invalid. And if you need to replay the  
> test
> after it, then it is the same as pressing the Stop button and replay.
> Right? So we are assuming the Pause button will not pause the current
> running threads but rather wait for actual cycle to finish and then  
> wait
> for a play.
> If so, the pause will not leave the Console. Remember that now each
> cycle is signaled by the console to the TestNode!


Pause is to temporarily wait on running the next test use case. Stop  
is to abort the test at the next test use case. Both use the snapshot  
mechanism.

I figure if it is really an emergency then the user can stop the  
TestNodes manually using some console like HP OpenView or the Windows  
process manager.


>
> 2. Local/Remote.  We can run the TestScenario locally (TM will  
> spawn the
> threads and run the methods) or remotely (TM will send the  
> TestScenario
> to the TestNode to be run by remote control). But we only have a play
> button. In TM 4.4 we have two play buttons, one for remote play.  
> What do
> you think?


The TestScenario.xml by default runs the test on the local node. It's  
up to the user to define the other nodes they want to run the test  
upon. That means we only need one play button.

By the way, there will also be a Run Script command in the Run drop  
down menu to run a Jython script. This is for developers working with  
the Recorder to test the function of a recorded or written TestCase  
before running it on a node.

-Frank





>
> William Martinez Pomares
> Architect
> Avantica Technologies
> Phone(US)  :+1 (650) 353-4522  Ext 131
> Fax(US)        :+1 (877) 372-1955
> Phone(CR)  :+506 283-9100 Ext 131
> Fax(CR)        :+506 253-7451
> http://www.avantica.net
>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.pushtotest.com
> http://lists.pushtotest.com/mailman/listinfo/dev
>



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



_______________________________________________
Dev mailing list
Dev at lists.pushtotest.com
http://lists.pushtotest.com/mailman/listinfo/dev