[hyades-dev] Meeting minutes for September 30th Hyades Execution Team M

[Kent D Siefkes <kdsiefke@xxxxxxxxxx>]

I have attached the meeting notes for today's execution team meeting.

Kent

Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, September 30, 2003

Attending
---------
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Dwayne Dreakford, IBM Rational Raleigh
Antony Miguel, Scapatech
Stephane Leroy, IBM Rational Toulouse
Sanjit Singh, SAP
Sonny Pak, IBM Rational Lexington
Todd Merriweather, IBM Rational Raleigh


Proposed Agenda
---------------
1. Review final status of Execution-related contributions for 1.1 release
2. Discuss 1.2 candidate execution enhancements, including changes to execution to support HTTP enhancements,
   and review execution-related review items already being covered in test model meeting from Joe Toomey's
   schedule.
3. Survey commitments for 1.2 contributions (design discussion and coding contributions)
4. Prioritize and allocate 1.2 candidate execution enhancements, propose slotting into iteration


Recorded Discussion/Decisons
----------------------------
1. Review final status of Execution-related contributions for 1.1 release
	- Joe - T8 (P1 1.1) Standalone execution capabilities which require no workbench interaction and
	  produce appropriate event logs.

		* Status: Complete, usage documention to be added later (see action item)

	- Ashish - HTTP extensions to JUnit runner for multiple instances

		* Status: Complete, 1.2 enhancements covered in last week's test model meeting (hierarchial
		  display in execution history viewer)

2. Discuss 1.2 candidate execution enhancements, including changes to execution to support HTTP enhancements,
   and review execution-related review items already being covered in test model meeting from Joe Toomey's
   schedule.
	Deferred from 1.1:

	• T7 (P1 1.1) Cross language linkage to the execution environment which implies any code generation
	  would be to these native languages. 
	• T4 (P2 1.1) Support a more interactive control model that allows execution to not only be started,
	  but also paused, restarted, stopped and cancelled. This will include events to reflect these
	  execution state changes.
	
	1.2 candidates:

	T3 HTTP load testing (beta P1 1.1, full function P1 1.2)
		HTTP enhancements (from http plans submitted to hyades-dev on Aug. 26th):
		- Cookie Handling
		- SSL playback
		  - OK to require JRE 1.4 for SSL record/playback, but must record/playback non-SSL with 1.3
		  - design with idea of leaving open the ability to provide a pluggable security provider later,
		    either use of RAC's (undocumented) model for pluggable security provider orsomething more
		    limited
		- User Timing Control (think times) [already submitted in 1.1]
		- Data variation (datapooling)
		  - OK to require manual Java coding (using datapool runtime APIs) to achieve this
		- Page level response time measurements
		- Simple scheduling (workload definition that uses individual http tests as building blocks)
		   - OK to use existing ability of a Hyades test suite to call other test suites, so this would
		     be satisfied by having an HTTP test suite call other HTTP test suites

	From Joe Toomey's test model schedule:

		- Datapool runtime API (subset of T5)
		
		
3. Survey commitments for 1.2 contributions (design discussion and coding contributions)

	Joe - participate in design discussion and some time for code contributions (20%), best fit is T4
	Antony - no time for coding, could participate in design discussion for T4
	Stephane - mostly interested in EJB deployment, no participation in coding or non-meeting design discussion
	Sanjit - SAP finishing Hyades evaluation, but not ready yet for contribution commitment
	Sonny - not ready for contribution commitment
	Kent - plan to contribute approx 2 virtual staff resources to HTTP execution work (out of total of 3
	       virtual staff allocated for Hyades HTTP), likely coming from Todd Merriweather's group

4. Prioritize and allocate 1.2 candidate execution enhancements, propose slotting into iterations

	T3 and T4 (equal priority, different resources, no conflicts)
	T7 (although P1, no contributors identified yet from execution team, relies on non-execution work as
	    well, Richard may be a source of contribution)

	Within T3, proposed priorities:
		Cookie Handling
		response time measurements (Page level is preferred)
		datapooling
		simple scheduling
		SSL
		

	Iteration 1: 9/29 - 11/7
		T4, including implemeting STOP for existing test types
		T3 part 1 (TBD)

	Iteration 2: 11/10 - 12/12
		T3 part 2 (TBD)

 
New Action Items
----------------
* Joe - document 1.1 ability to execute tests standalone (command line)
* Kent - talk with Richard Duggan about T7 staffing