From: Santosh D. <san...@gm...> - 2005-07-27 07:50:29
|
On 7/27/05, Cerecke, Carl <car...@hp...> wrote: > Hi, >=20 > Because many tests may have a common starting sequence, it would be > useful to be able to pause playback, then record some actions. As far as > I can tell, marathon does not have this ability. An alternative to this would be to use the capture script functionality. If you have a common starting sequence and need to record this repeatedly (such as login). you could record this as a capture script and then insert it in every recording you do. hope this helps >=20 > Also, I have added some useful features to marathon for playback. One is > an "interactive()" script which pauses playback and pops up an > interactive jython console where components can be interactively queried > (and changed, if you really want). When the console is closed, playback > resumes as normal. Another feature, which can be called from within the > console, is a jython function which generates tests for all the testable > components in a window. These generated tests can then be inserted into > a script. Saves having to click on every little thing during a record to > check everything. > interesting thought. can you send me the scripts ? =20 > Anyway, the killer feature marathon needs is a way to jump from playback > to record. >=20 > If this is just a matter of hacking some code, then I can do it. If it > requires a big reorganisation of the marathon internals, I don't have > the time. If anybody has a feel for the size of the task, please let me > know. >=20 regards santosh s |