RE: [hyades-dev] external behavior, was: goals for script/record/play

[Julien Canches <julien.canches@xxxxxxxxxx>]

We are using the external behavior feature
in one of our projects.
Basically, the model specifies that
each test has a behavior, and this behavior may be either described in
the model itself, or points to an external resource that describes the
behavior.
If the behavior is an external resource,
it is up to the extension to specify this external resource format, how
it is generated and how it is handled for the purposes of code generation
and execution.

What you loose by choosing the external
behavior thing is the ability to reuse some UI components (mainly the Test
Suite Editor), and the compatibility with a model aligned with UML2 concepts.
But this is not necessarily the "poor man's way" into Hyades,
it allows Hyades to interact with external tools that specify tests in
a format of their own.
In the case of Abbot for instance, you
may consider either the Abbot Test Suite (the JUnit source) or the .xml
script as an external behavior of your test. And then, in the future, provide
some bridge between your external behavior and the Test Model's internal
behavior.

Regards,
Julien

==
Julien Canches
Software Engineer
Rational Software ASQ
IBM Software Group


hyades-dev-admin@xxxxxxxxxxx wrote on 17/09/2004 15:33:51:

> James,
> 
> The in principle answer is Yes, but I don't know if the codegen or
UI 
> actually support it.
> 
> Tom, 
> 
> External behaviours come in from the U2TP specification, 
> http://www.fokus.gmd.
> de/u2tp/Related_Documents/UMLTestingProfile_FinalSubmission.pdf
> 
> The above may not help you unless you have the UML context and 
> additional understanding of the implementation.  I've attached
a 
> document which I have pulled from an early unfinished white paper
and 
> updated to reflect more recent changes.  It's not going to be
perfectly 
> correct or complete but it may help.
> 
> MIke
> 
> 
> -----Original Message-----
> From: James.Saliba [mailto:James.Saliba@xxxxxx]
> Sent: 16 September 2004 22:00
> To: hyades-dev
> Subject: RE: [hyades-dev] external behavior, was: goals for
> script/record/play
> 
> 
> Talking about external behavior, can Hyades be used to kick-off a
> command line driven test?  
> 
> Regards,
> Jim Saliba
> 
> -----Original Message-----
> From: hyades-dev-admin@xxxxxxxxxxx [mailto:hyades-dev-admin@xxxxxxxxxxx]
> On Behalf Of Thomas L Roche
> Sent: Thursday, September 16, 2004 2:19 PM
> To: hyades-dev@xxxxxxxxxxx
> Subject: [hyades-dev] external behavior, was: goals for
> script/record/play
> 
> Michael.Norman Thu, 16 Sep 2004 14:04:49 +0100
> > Anyway, quite obviously I have limited knowledge of JUNIT
> > derivatives although some of our guys have worked with Abbot
in
> > particular and were very positive about it and in fact we support
it
> > as an external behaviour to our existing commerical testing tool
> > (which in turn is an external behaviour as far as Hyades is
> > concerned), and we have a bunch of additional APIs which filter
back
> > through a circuitous route into the Hyades Execution History.
> 
> Could you (or delegate, or someone on this list) point me toward more
> information about the meaning of "external behavior" in
the Hyades
> context, and how they work? Sounds like it might be "the poor
man's
> way" to plug into Hyades--satisficing though perhaps suboptimal.
> 

> [attachment "TestIntro.doc" deleted by Julien Canches/France/IBM]