[ptt-users] Testmaker 5 B2

[Dominique de Waleffe]

Frank Cohen wrote:
> Hi Dominique: Which JVM are you running? Would you willing to send me 
> the recorded script? Is the site you recorded available on the public 
> internet?

I am running on Sun 1.6.0.

The script I recorded is against an internal application, however there 
is nothing secret about the script and I believe nothing special about it...

I sort of found a way out of this (and reported bugs on trac related to 
the issue).

- It appears that the TestMaker.properties file got somehow corrupted 
(but I can't see what's wrong). So I moved it away and was able to start 
again... (trac issue 85). Found that this was related to the properties 
file by starting under jdb but could not pinpoint more precisely the 
problem...

- I could start the tesgen4web directly without importing it

- I could not however run the imported as jython file derived from the 
above script (trac issue 86)

> 
> By the way, I'll be on vacation until Sunday (it's the US Independence 
> Day weekend here.)

Have a good W-E then.

D.

> 
> On Jul 5, 2007, at 7:50 AM, Dominique de Waleffe wrote:
> 
>> Hi,
>>
>> I imagine some of you are also trying to use the new version of 
>> testmaker, so I post here before filing this as a bug hoping to get 
>> some info first on how to progress...
>>
>> I have installed B2 on Windows Xp.
>>
>> I was trying to have a scenario recorded via testgen4web, and imported 
>> from the menu [import tesgen4web], thus translated to jython, run as 
>> an agent so I clicked on the 'run agent' menu. TM said it needed to 
>> initialize some stuff for scripting. Then TM was in a strange state 
>> (could not edit files anymore,....) I thus stopped it and tried 
>> restarting.
>>
>> Now TM seems to start but dies without having opened anything and 
>> without leaving a single message on the console...
>>
>> Has anyone seen this?
>> Is there a log file anywhere?
>> What should I do? I hope re-installing will solve this but if I can 
>> first find some extra info for debugging this state, that would help. 
>> Any hints?


-- 
Dominique de Waleffe