[hyades-dev] Meeting minutes for 4/28 Hyades Execution Histories Model S

[Ashish K Mathur <akmathur@xxxxxxxxxx>]

Attached are the meeting minutes from
the first team meeting of the Execution Histories Subgroup.




Regards,
ashish
------------------------------------------------------------------------
Ashish K. Mathur
IBM - SWG - Rational Division
Phone: (919)845-3213      Fax: (919)845-3250
Email: akmathur@xxxxxxxxxx
Execution Histores Model Subgroup, 28-Apr-2003

Attending
---------
Joe Toomey - IBM Rational Lexington
Antony Miguel - Scapa
Gian Franco Bonini - SAP
Marcelo Paternostro - IBM Toronto
Stefan Daume - Scapa
Kent Siefkes - IBM Rational Raleigh
Ashish Mathur - IBM Rational Raleigh


Recorded Discussion
-------------------

- Ashish Mathur will be the subgroup leader.
- Agreed on the need for an API to log a test case verdict, which does 
  not assume a modeled behavior.
- Must be near finalization of execution history model within 2 weeks 
  to allow UI team to build UI.

Minimal Use cases to address for Hyades 1.0.0:
---------------------------------------------
1) Must be able to add name and description to execution history 
   before or after test run.
2) A Running test must be able to log all events defined by execution 
   events subgroup.
3) Must be able to view the execution history log after the test run.
4) Must be able to view execution histores in hierarchical folders 
   (resource navigator)
5) Must be able to navigate from TestSuites to Execution Histories 
   of that suite
6) Take requirements from UI Reporting group (to ensure that the data 
   needed for reports is captured.)
7) Need to allow navigation from Execution History to Execution 
   Traces (if it exists)
8) Need to allow gesture to "promote" verdict(s) from execution 
   history to Test Model persisted verdict(s)



* U2TP portion of Test Model will be realized in Execution History 
  model via API calls for start and stop of test case and test 
  suite.  Require at least a test suite start, test case start 
  end, test suite end
* For logging behavior, allow looging with IDs (that map to 
  modeled behavior), also allow use of specific log apis to indicate 
  test case behvaior structure (log(LOOP_START)).  Both are optional.


Questions
* Can we create a test agent?  (who would write it?)  Other 
  alternatives are to use the Logging agent?
* Who's writing the loader?
* Who's writing the APIs?
* Who's defining the XML fragments?
* Who's writing the UI?
* Who's writing the agent (if we need one)?


Actions
-------

Ashish - Determine weekly meeting time, schedule meeting, send invitation.