RE: [hyades-dev] [YOUR ACTION REQUIRED] Discussion points from Tu esday'

["Toomey, Joe" <jtoomey@xxxxxxxxxxxx>]

Hi Mike,

Thanks for your feedback.  My comments below:

--Joe

Joe Toomey
Senior Staff Software Engineer
Rational Software
IBM Software Group
tel: (781) 676-7668
fax: (781) 676-7640



> -----Original Message-----
> From: Michael Silverstein [mailto:msilverstein@xxxxxxxxxxxxxx] 
> Sent: Wednesday, March 26, 2003 11:40 AM
> To: hyades-dev@xxxxxxxxxxx
> Subject: RE: [hyades-dev] [YOUR ACTION REQUIRED] Discussion 
> points from Tuesday's Executio n Team meeting:
> 
> 
> 
> > -----Original Message-----
> > From: hyades-dev-admin@xxxxxxxxxxx 
> > [mailto:hyades-dev-admin@xxxxxxxxxxx] On Behalf Of Toomey, Joe
> 
> > 4) Semantic of IExecutableObject.getChildren().  We agreed that
> > IExecutableObject.getChildren() would only retrieve the 
> > direct children of the IExecutableObject on which it was 
> > invoked.  We also agreed that it may be worthwhile to expose 
> > an additional API to walk the tree and retrieve all of the 
> > children, although a client could obviously implement their 
> > own traversal.  Thoughts?
> > 
> 
> I'm just starting to get into this so please pardon me if I'm covering
> ground already well trodden.
> 
> In SilverMark's Test Mentor we represent tests as multiply 
> nested trees
> of steps. Over time, we have found it necessary to provide 
> the following
> APIs for accessing steps:
> 
> - Immediate children
> - All children
> - Enumerator or Iterator for immediate children
> - Enumerator or Iterator for all children
> - Access a step given a path of parent indices. This is used 
> to execute
> any arbitrary step within the tree, by itself.
> 
> We've also found it necessary to implement APIs that provide 
> access to a
> step's parent as well as the top-level parent.
> 
> There are others but it looks like the topic is access to children so
> I'll stop here.

JPT> First, I should correct my error in saying that the interface in
question was IExecutableObject.  It was, in fact, IExecutionComponent that
we were discussing.  Having said that, these interfaces are part of the core
execution framework.  IExecutionComponent.getChildren(), in particular,
returns other IExecutionComponents, and IExecutionComponents are not tests.
IExecutionComponents are Hyades Components that are used during a test run,
or during a profiling session.   An agent gathering trace data would be one
example of an IExecutionComponent.

JPT> If you're interested in the way that we're currently representing
tests, you should take a look at the test and common packages of the Data
Models that were published to the Hyades website this week.  The test
package shows our proposed implementation of the UML2 Testing Profile, and
the common package contains the behavioral data model (which is essentially
UML2 interactions.)

http://dev.eclipse.org/viewcvs/indextools.cgi/~checkout~/hyades-home/docs/co
mponents/data_models/data_models.html

JPT> To see more about how the proposed Execution API will work, please also
take a look at what was published for the Execution Environment group this
week.  It includes Javadoc for the proposed interfaces, and a sequence
diagram use case realization for a very simple use case.

http://dev.eclipse.org/viewcvs/indextools.cgi/~checkout~/hyades-home/docs/co
mponents/execution_environment/execution_environment.html

Thanks,
--Joe

> 
> -----------------------------
> Mike Silverstein
> SilverMark, Inc.
> The Object Testing Company
> www.javatesting.com
> **********************************
> * Providers of the "Test Mentor" *
> * Java component testing tool    *
> **********************************
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.462 / Virus Database: 261 - Release Date: 3/13/2003