| [hyades-dev] Hyades Execution Meeting Agenda for Tuesday 11/23 at 11 am ET (Meeting notes for 11/16 meeting attached) |
International
Access/Caller Paid Dial In Number: (210) 839-8980
HOST/PASS
CODE: 70499
e-meeting details follow at the bottom
of this note.
Proposed agenda:
1. Review design on integration of Test
Harness and Profiling - Scott Schneider
I've also attached the meeting notes
from last week's meeting.
Thanks,
Kent
Kent Siefkes
Rational Software
IBM Software Group
Phone: 919-486-3233, IBM T/L 526-3233
------------------------------------
------------------------------------
PREPARE FOR THE WEB CONFERENCE
Customers, business partners and vendors:
+ When joining the web conference, you will be asked for an IBM
ID and password.
- To verify an existing IBM ID and password, please visit
http://www.ibm.com/account/profile
to ensure valid sign in credentials and review your
registration information.
- If you need a new IBM ID and password, visit http://www.ibm.com/account/profile/us?page=reg
to register. The ID should be active for usage on
http://www.ibm.com/collaboration/collaboratenow
within 10 minutes of submission.
+ If this is your first IBM Web Conference, attend the special
"test" meeting to
make sure that you can join easily. Please visit http://www.ibm.com/collaboration/collaboratenow
and click "test meeting"
+ To join the conference, a Windows 2000 or Windows XP computer
is required.
IBM employees:
+ Please use your w3.ibm.com intranet ID and password.
+ If this is your first IBM Web Conference, attend the special
"test" meeting to
make sure that you can join easily. Please visit http://w3.ibm.com/e-meetings/webconferences
and click "Connectivity Test"
JOIN THE WEB CONFERENCE
1) Join the conference up to 15 minutes prior to 11/23/2004 10:45
AM (UTC -5)
2) Direct your web browser to the following URL:
https://www.ibm.com/collaboration/webconferences/meetingdetails.jsp?meetingId=5E76B4FC70DAD7BDACF65E27DA335269
3) When asked, enter your user name and password. Customers
use your IBM ID.
4) When prompted, enter the web conference password: hyad3s
Additional web conference details:
Conference name: Execution Meeting
Password: hyad3s
Start time: 11/23/2004
10:45 AM (UTC -5)
Duration: 1h 15m
IBM Confidential? No
Meeting Manager: scott.schneider@xxxxxxxxxx
Moderator: scott.schneider@xxxxxxxxxx
Tools: Whiteboard,
Screen sharing, Public chat, Send web page, Polling
Attachments: None
NOTE: If a participant has lost the e-mail with the conference URL
and password,
you may join the meeting using the following
steps:
Customers, business partners and vendors:
- Visit http://www.ibm.com/collaboration/collaboratenow
and sign-in.
- Enter the exact meeting name (case
sensitive) into the empty text field in
the web conferences portal.
IBM employees can browse and search
for the conferences at
http://www.ibm.com/collaboration/webconferences/list.jsp
END THE WEB CONFERENCE
After the Web Conference has completed, all moderators should be
sure to end their
Web Conference. Ending a Web Conference disconnects all users,
and stops all
associated usage charges at that time. A meeting can even
be ended earlier than
its scheduled duration to save on conference related costs.
For detailed information on how to properly end a web conference,
please visit:
https://www.ibm.com/collaboration/webconferences/webconfhelp31.nsf/html/extend_or_end_an_active_meeting.html
BEST PRACTICES AND SUGGESTIONS FOR THE MEETING MODERATOR
Please review the following best practices to ensure a successful
web conference:
http://www.ibm.com/collaboration/webconferences/help/
To make a suggestion or ask questions, visit
http://w3.ibm.com/e-meetings/webconferences/help and select "Discussion
Forum."
IBM Web Conferences is powered by the IBM Lotus Web Conferencing product
--
http://www.lotus.com/sametime -- and hosted by IBM Global Services.
Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, Nov 16, 2004
Attending
---------
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Scott Schneider, IBM Rational Lexington
Eugene Chan, IBM Rational Toronto
Valentina Popescu, IBM Rational Toronto
Martin Boag, IBM Rational UK
Julien Canches, IBM Rational Toulouse
Proposed Agenda
---------------
1. Discuss integration of test harness and profiling
2. What sort of refactoring would we like to see happen on the profiling to leverage on the execution side? < didn't get to this >
Recorded Discussion/Decisions <post-meeting annotations>
---------------------------------------------------------
Discussed two different use cases that relate to test harness and profiling integration:
UC1. Profiling a running test (we will profile the test that is being launched - only)
- what does it mean to profile for the various Hyades tests?
- JUnit test - collect profiling data on the application that is stimulated by the JUnit test
- URL test - not as useful for traditional profiling, but still may be useful for URL test developers or people that want to understand how it works
- primarily useful for probekit extensions to gather other non-profiling types of data collection
- Manual test - n/a
UC2. Execute a test and have zero to many data collectors running at the same time on multiple machines (not limited to machine where test is running),
and that data would be integrated with the execution results
- Launch config integration - configuration information for the data collectors would be combined with the configuration of the test
- so that the user can have various configurations for running the test (one with no data collection, one with full data collection, etc.)
- The data collector(s) would be invoked by the test harness on the associated machine(s). Different data collector combinations can apply to different
machines.
- Integrated Test results - user names one location for execution results, and is able to navigate to various trace model and stats model data from a single execution results
- This use case applies to JUnit, URL Test, Manual Test, and any vendor added test type
Decided to split out UC1 into a new enhancement request (it was added to this enhancement, which was originally limited to the UC2 intent), and have it considered for 3.3 (following normal process)
- Scott will file enhancement request added to bugzilla today, description page targeted by end of week
What data collectors would be offered to user (to attach to configuration)?
1. Use discovery to determine what collectors are available on the listed machines. To keep in scope for 3.2, will require connection to machine(s) to determine which data collectors (Agents)
are available on that machine
New Action Items
----------------
* Scott will file enhancement request for UC1 < this made the 3.3 consideration list >
* Kent will file enhancement request for advanced discover & deploy mechanisms for UC2, targeted for 3.3 < too late for deadline for 3.3/4.0 >