RE: [Logitest-developer] Features added

[Anthony E. <me...@an...>]

> 
> I haven't used eTest, did they do a character by character 
> diff or something 
> with more tolerance?

I believe it was line by line.  If I recall correctly they parse the
HTML (similar to running it through HTML Tidy), convert it to all caps
and then compare that with the last run.
 
> > [snip]
> > > > - The temp file addition to the SaveThread always fails on my
> > >
> > > machine (and
> > >
> > > > thus I cannot save).
> > >
> > > Can you give me a stacktrace?  It seems to work fine for me.
> >
> > Sure:
> >
> > java.io.IOException: Could not backup file to 
> > C:\DOCUME~1\ANTHON~1\LOCALS~1\Temp
> > \logitest55082.xml
> >         at org.logitest.ui.SaveThread.run(SaveThread.java:91)
> >
> > Not very descriptive though.  :-)
> >
> 
> You're right - not very descriptive.  I'll see what I can do.

For the moment I took it out of my version of the code.  I would like to
be able to put it back in though.  I await your changes.

> 
> >
> > A couple suggestions as well:
> >
> >  - The hot key for the start and stop recording is the 
> same...perhaps 
> > the stop recording button and menu item should be disabled 
> until the 
> > record button is hit.
> >  - It would be nice to have something indicate that you are 
> recording. 
> > Originally I had a little "RECORDING" flashing in the bottom of the 
> > window, next to the progress indicator, but you are welcome to do 
> > something else.
> >  - If I record and then type a link into the address field 
> the page comes
> > up but is not added to the test tree.
> >  - You may want to allow the delay between user clicks 
> while recording to
> > be stored and used as the pre-load delay.  Users should be 
> able to enable
> > and disable this feature.  The pre-load feature allows the 
> playback to
> > occur in a more realistic fashion (i.e. simulate user delay).
> 
> Will do.
> 
> > All in all though I really like the recording.  I am glad 
> someone did 
> > it.
> >
> > :-)  I am curious about your "added support for variables" 
> comment in 
> > your
> >
> > CVS entry...what exactly is it?
> 
> At this stage variables are only supported in URLs.  I needed 
> them because 
> the site that I am testing uses a system assigned session ID 
> in the URL 
> (rather than cookies).  When I test my site the login page is 
> loaded and this 
> has a session ID as part of the login form's action URL.  I 
> use a "Regex 
> Variable Reader" to read a value for the variable SESS from 
> the page using a 
> regular expression.
> 
> In the test properties dialog I set the session substitution 
> command to 
> replace any session IDs in recorded URLs with $SESS$.  Hence when the 
> recorder adds resources they have $SESS$ instead of the 
> session ID.  When the 
> browser opens these resources it substitutes $SESS$ with the 
> value read by 
> the variable reader on the login page.
> 
> While variables are only substituted in URLs at this stage I 
> imagine it could 
> be useful to allow them to be substituted in request 
> parameters (i.e. post 
> data) as well.  This means you could read a variable of one 
> page and then 
> submit it as part of the post request on another page.

What are you using for variable insertion?  Perhaps we can use Velocity
for all variable substitution.

-Anthony