[cdt-test-dev] RE: CDT Testing process

[Mathieu Lapensee <lapensee@xxxxxxxxxx>]

James,

The Sanity Test Suites were for CDT
2.0.x.   They will need to be updated for CDT 3.0     However,
I don't think there will be a lot of changes.

As a start, anything in the UI section
 in the CDT 3.0  milestone plan  (http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt-home/plans/3.0/milestones.html?cvsroot=Tools_Project)
  
will need to be added  to the sanity
test suite.  For example,  Drag & Drop from the C/C++ Projects
View should be included.

Regards,

Mathieu Lapensée
Software Verification Developer
IBM - SWG - Rational Division

James Tan <jtan@xxxxxxx>

03/03/2005 12:18 PM

To	Brent Nicolle/Ottawa/IBM@IBMCA, Mathieu Lapensee/Ottawa/IBM@IBMCA
cc	cdt-test-dev@xxxxxxxxxxx
Subject	RE: CDT Testing process

Sounds like a good plan, Brent.
Thanks.
 
So I guess I can use the sanity
testplans(Level 1 and level 2) I got from Mathieu. Since I didn't participate
previous CDT test, I am not sure the sanity testplans are up-to-date, Is
there anything you foresee that  we need to add to the sanity testplans,
Mathieu?
 
Thanks guys,
James
-----Original Message-----
From: Brent Nicolle [mailto:bnicolle@xxxxxxxxxx]
Sent: Thursday, March 03, 2005 10:49 AM
To: James Tan
Cc: cdt-test-dev@xxxxxxxxxxx
Subject: RE: CDT Testing process


Hi James, 

Unfortunately, I'm buried in product testing and CDT has slipped off of
my radar screen.  I think my schedule has a little more slack by March
21st. 
Consequently, I doubt if I'll personally have time to participate in M5
testing (at least in a timely fashion), or even to coordinate a testing
conference call. 

If you want feedback on what you think you should be testing in M5, and
when to start and stop, cdt-test-dev is a good place to ask. I'm CCing
them here for any other feedback.  Otherwise, cdt-test-dev is a pretty
quiet mailing list these days. 

I don't like delegating work when I won't be participating, but I propose
the following: 
1. Tue Mar 15th, remind cdt-dev to hold off big checkins for a day or two.
2. Download the M5 Eclipse build and the Tuesday CDT build.  
3. Run a quick one-hour all-around sanity test and report any findings
to cdt-test-dev and cdt-dev, summarized by a SanityThumbsUp (so others
can know it's good for testing) or SanityThumbsDown (so that others can
fix the showstoppers and rebuild).   
4. Alert cdt-test-dev that you are starting a day or so of Milestone testing
specifically in say Memory View testing, if that's going to be ready (or
partially ready) by M5. 
(Other contributors should follow suit.) 
5. After a day or so, summarize your test results to cdt-test-dev with
a ContributorThumbsUp (or a ContributorThumbsDown).
6. Once all test contributors have given their ComponentThumbsUp, you can
summarize to cdt-dev and cdt-test-dev with a MilestoneThumbsUp.
This is dev's cue, to officially declare M5 and to start checking-in code
for M6. 

How's that for a plan? 

- Brent

James Tan <jtan@xxxxxxx>

03/03/2005 10:05 AM

To	Brent Nicolle/Ottawa/IBM@IBMCA
cc
Subject	RE: CDT Testing process

Hello Brent, 
  
Just want to touch base with you guys about CDT3.0 testing. 
  
I am writing test plan for features committed by Alain and Mikhail. Currently
working on memory views. For CDT M5, I wonder if any test effort we would
provide. Suppose M5 is still on Mar 14th, what would be the test schedule.
  
It seems I am not getting anything from cdt-test-dev, are we still using
this newsgroup to coordinate the test effort and when will be the next
conf. call? 
  
  
  
  
Thanks, 
James