| [hyades-dev] Meeting minutes for 5/20 Hyades Execution Team Meeting |
|
I've attached the meeting notes for this Tuesday's meeting.
Kent Siefkes
|
Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, May 20, 2003
Attending
---------
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Anthony Miguel, Scapa
Victor Haven, IBM Rational Cupertino
Richard Duggan, IBM Toronto
Dwayne Dreakford, IBM Rational Raleigh
Proposed Agenda
-------------------------
1. Quick update on status of coding progress from Dwayne and Antony (with input on Richard's side as well)
2. Implementation schedule deadlines
3. "Test Tool" - Implementation status (UI Team)?
4. "WSAD Component Test" Executor(and Execution Environment?) Status [Kris returning 5/28]
5. Execution issues related to Execution History
6. Review high level plan (for remaining Rel 1 todo)
1. Scope execution use cases for Release 1 (Eclipse release 2.1.1) completed April 8, 2003
UC1 - Launch a single test instance from workbench on a single specified node
UC1.1 - Show control events to running test
UC2 - Monitor a running application on a specified node
UC2.1 - Show control events to monitored app
UC4 - Launch a test for immediate reporting/monitoring
2. Share and align/confirm use cases for Release 1 with User Interface group completed April 11, 2003
3. Participate in overall Hyades schedule/planning for first release ongoing
4. Complete and review remaining use case realizations, interfaces, and java doc for use cases scoped in
for first release.
5. Specify control events for controlling execution (UC1.1) and monitoring/profiling (UC2.1)
6. Identify APIs for components that run on the remote machines, in conjunction with the Data Collection
& Communication group.
7. Add to our use case realizations interactions with the remote side components
8. Build reference implementation (integrating with the UI group and Data Collection & Communication group)
to realize the Release 1 execution use cases (UC1, UC2, UC4, UC1.1, UC2.1), including the implementation
of the associated execution interfaces (workbench side).
Recorded Discussion/Decisons
----------------------------
1. Coding progress update:
*Dwayne - marshalling and skeleton/stubs framework completed,
a couple of hours away from completing the Agent listeners, then need to integrate with RAC, and then integrate with
Kris's Executor for JUnit to get to "Hello World" end to end demonstration
*Antony - finished additional exceptional handling on Session components and transferred to Richard, who will merge & drop
2. Implementation schedule deadline discussion
* This week's committer meeting delayed until Wed. 12:30 pm ET, Dwayne should get changes to Richard by Tuesday night for merging, but
continue up until committer all for dropping Wed. afternoon
* Treat next week's drop as the final functionality drop for Rel 1 (other than defect fixing), unless we hear otherwise
3. "Test Tool" - Implementation status (UI Team)?
* Due to special UI meeting at same time this week, no UI rep to report status, to follow-up after meeting with Marcelo
4. "WSAD Component Test" Executor(and Execution Environment?) Status [Kris returning 5/28]
* 1. JUnit - Dwayne (next step after integrating with RAC, per #1 above)
* 2. HTTP (implemented as Java, so almost identical to JUnit) - Dwayne (to look at after JUnit is complete)
* 3. Manual - Joe offerred to look at this after the test model facade is finished and if JUnit/HTTP completes before Kris returns
5. Execution issues related to Execution History
a. Need for Execution Results ID to be passed to ExecutionComponents (at least Executor) in order for loader to store incoming Execution
Events into appropriate ExecutionResults' Execution History. How do we pass that down the chain?
* Need to talk with Marcelo later in the day in the Execution History meeting.
b. Who is writing Execution Events out in sample Executors ?
* Dwayne will look at this after JUnit/HTTP basic execution is working, discuss offline with Marcelo and Ashish.
c. Who is implementing the loader for Execution Events? Who is implementing the viewer?
* Follow-up with Marius for loader
* Follow-up with Marcelo about the viewer
d. Who should obtain and store Version info into the ExecutionResults for a test case / test suite? It seems that if we generalize to
external behavior, that only the Executor (or related per test case type component that creates the ExecutableObject) knows this.
Probably needs to be deferred post R1.
* Agree to defer post R1
6. Review high level plan (for remaining Rel 1 todo)
4. Complete and review remaining use case realizations, interfaces, and java doc for use cases scoped in
for first release:
* UC1, UC1.1 and UC2 already dropped [minor updates needed, e.g. factory for Executor, agreed to defer post next week's
code drop]
* UC4 and UC2.1 remain.
* Do we scope out UC4 and 2.1 for Rel 1? Topic for joint Execution-UI discussion later this week, but Richard felt we needed
to scope out 2.1 for Rel 1
5. Specify control events for controlling execution (UC1.1) and monitoring/profiling (UC2.1)
* Only UC2.1 monitoring/profiling control (filtering) remains, but not needed for Rel 1 if we scope out 2.1 UC per above
6. Identify APIs for components that run on the remote machines, in conjunction with the Data Collection
& Communication group.
* Richard thinks this is complete and has been JavaDoc'd, but it may not be gen'ed and dropped yet. Decided we can clean this
up with next week's drop.
7. Add to our use case realizations interactions with the remote side components
* Remaining todo, decisions have been made and info is now available, but agreed We can and should do this AFTER our deadlines
for Rel 1 code
8. Build reference implementation (integrating with the UI group and Data Collection & Communication group)
to realize the Release 1 execution use cases (UC1, UC2, UC4, UC1.1, UC2.1), including the implementation
of the associated execution interfaces (workbench side).
* in progress, although at least UC2.1, and possibly UC4 will be scoped out for Rel 1.
New Action Items
----------------
* Kent will contact valentina to set up a meeting to coordinate remaining implementation work with the UI group