[OpenSTA-devel] Re: Codemax

[Federico T. <ft...@fi...>]

> That is the normal/good way to validate a Web transaction...
>
> However, often doing this causes problems because specific Web
> applications may be very dynamic in the HTML they create and trying
> to match to a DOM identifier will fail even though the transaction
> was successful.
>
> The alternative is to not use a DOM identifier, to dump the whole
> body, and then to use ~LOCATE, ~EXTRACT, etc. to pull out your text.
> The problem with this can be that you are limited to the first 64K of
> content...
>

Perfect, an other good issue, but it is not what I want.

Let me say that the system that I tested was made with autogenerate code.
It has a lot of HTTP trafic and parameters. Some times, I made chages
to the original script to parametrize, but this didn't work. Or
perhaps it works fine to one VU but not with 2 or more VU.
Using BView we can debug a lot of the script running alone. I want to
a facilitie to debug a script that has problems to run with two or
more VU.
I want to see the pages, complete html pages, that the server return
with error (aplication errors), that dont pass the test case.


> > > The Modeler can already use an ODBC data source to populate an
> > > FVR file - is this the area you would like to extend?  Or would
> > > you want to integrate into the Commander, or just be another
> > > seperate tool?
> >=3D20
> > ok, but the functionality that you say in the Modeler populate an
> > FVR at the moment that we create the variable.  After an execution
> > we can not update the contenent of a FVR quickly and easily.
>
> OK, I think the "right" initial way forward is to expand the
> Modeler's existing facilities to make it possible to update the FVR
> contents at any time in the most flexible manner.
>

I'd like to expand the Commander with this facilitie, because I want
to update all the variables existing in all the scripts contained in a
Test. Previusly we could set a couple of parameters, and then just
with a click update all the FVRs correspondig.


> Warning: there are bugs associated with the whole FVR updating and
> usage area.  Check the bug database.

I know the bugs, and I had to use the workarrounds

>
> > Now I use my tool as a separate tool, but could be good that all be
> > together in the same toolset, perhaps as a part of the Commander.
>
> An important part of any features you provide in this area should be
> a command line interface.  Many people run their tests in "batch
> mode" where they are not interested in the GUI at all - this type
> of usage is a key element of OpenSTAs future goals.
>

Ok, thanks

saludos!
fedeFede