[OpenSTA-devel] Re: Codemax

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

Federico Toledo wrote:
> I will explain a little more.
> In some cases, in a execution I see that the server return
> aplication's errors and so the test case fail.

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.

> If I want to know why it fails, what try to say me the aplication,
> I can't.  For example, to do this to one VU I use BView, because I
> can view the pages returned by the aplication.  It's alright.  But
> if I run the script with two VU and there are problems, because the
> aplication fails with concurrents users (for example too), I'd like
> to view the pages with error to detect the error.  The easiest form
> to do this is that OpenSTA save this pages automatically.  I hope
> that you understand me.

I think I understand what your intentions are, I just can't
understand how you intend to spot the error automatically.

> > Of Course you can do something like this now by saying:
> >   LOAD RESPONSE_INFO BODY ON ConId INTO VarName, &
> >     WITH DomIdentifier, RETURNING STATUS RetStat
> >   IF (RetStat < 0) THEN
> >     LOAD RESPONSE_INFO BODY ON ConId INTO VarName
> >     LOG VarName
> >   ENDIF
> > but perhaps something more elegant and automatic would be much
> > more useful.
> 
> Ok, that's a good idea, that could help me with other problems, but
> it isn't what I want.

If you want to do something that it is not caused by contents of the
returned HTTP Reponse body; say you want to make your condition on
the HTTP return code then you just need a ",RETURNING CODE HttpCode"
on your SCL HTTP request command, then change the conditional based
on this return.  If you did base it on HTTP error code then for many
codes the returned BODY would not be at all helpful.  Does that help
you more?

If not, give us more of a clue of what the condition you would base
your "failure log" on.

> I supouse that you like me parameterize your scripts, and get your
> values from file.
> This files you have to generate with some data from DataBase with
> the corresponding SQL.
> I have 10 .fvr with parameters.  After each execution I have to
> refresh the contenent of this 10 archives.  My tool gets the SQL
> from a file (acording how you configure a XML), and execute this
> and save the result in the corresponding .fvr.
> Before I made the tool, I take 10 minutes to do this job, and now I
> take 1 second to press the buton.
> I made this and anothers tools in java, but could be better that we
> can integrate all of this to OpenSTA.

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?

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