[OpenSTA-devel] Re: Codemax

[Daniel S. <da...@Op...>]

Daniel Sutcliffe wrote:
> > OK, so this is the key question: these "application errors", what
> > signifies them?  Because, as far as I am concerned there is no
> > standard way of reporting Web application errors - HTTP error
> > codes certainly normally have little relation to Web application
> > errors.

Federico Toledo wrote:
> In my case, for example, I want to receive a page with the message
> "Facturaci=F3n completa" so I use a Load response info ... and compare
> the string.

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...

> But if the load response info fails because not match with the page
> I can't know what happened.  I could save a log...

This is the code fragment I provided earlier.

> but I want to save the HTML page in the case that fail the load
> response info ... or fail the test case, and then, after of a
> execution, I could see the pages returned in each error.

The real problem you face with writing out a complete file after a=20
script action is that of doing file IO from SCL.  The problems that
exist in this area are mostly related to the potential distributed
nature of Script execution.

> This facilitates the concurrence test more than the stress test.
> Ok?

I think it is acknowledged that even in stress/load testing you need
to know at what point things start to fail ...

> Understand my intention?

I totally understand your intention, and think I always have.  I'm
still not sure of what you would like to implement though.

> > 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?
>=20
> 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.

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

> 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.

Cheers
/dan
--=20
Daniel Sutcliffe <Da...@Op...>
  OpenSTA part-time caretaker - http://OpenSTA.org/