Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-releng] Smoke Test Request for WTP 3.2.0 I-build towards M1

Typically, someone on the team follows their documented smoke tests at and executes all or 
part of that test. The expectation (for an early I-build) is to confirm 
the main paths work before being embarrassed by someone picking it up and 
then discovering, for example, that an editor crashes right away. 
Typically, smoke tests should take less that 30 minutes. 

And then that person edits the smoke tests page; using the checkmark 
graphic if they agree the build is worthy to promote (i.e. is ok for 
adopters or others to pick up for continued development or more in depth 
testing). a red X (and bug number) is used if not worthy, in which case 
the expectation is that bugs will be open and a fix will be forthcoming 
and a respin would be required before promoting. Sometimes, a "pass" 
(checkmark) is given along with a bug number, which means basically the 
person thinks ok to promote as-is, but gives a "warning" that some 
regression or bad bug was discovered that others might want to consider 
before blindly adopting or doing more in depth testing. 

Hope this is the kind of information you were looking for. Feel free to 
ask followup if not. 


Wtp-Releng <wtp-releng@xxxxxxxxxxx>
07/09/2009 11:14 AM
Re: [wtp-releng] Smoke Test Request for WTP 3.2.0 I-build towards M1
Sent by:

What is involved in the "testing and approval" part of the task?  Is there 
a procedure for this?


----- Original Message -----
From: "David Williams" <david_williams@xxxxxxxxxx>
To: "Wtp-Releng" <wtp-releng@xxxxxxxxxxx>
Sent: Thursday, July 9, 2009 6:42:24 AM GMT -08:00 US/Canada Pacific
Subject: [wtp-releng] Smoke Test Request for WTP 3.2.0 I-build towards M1

Smoke Test Request for WTP 3.2.0 I-build towards M1

Please document your Project&apos;s testing and approval of our 3.2 
by today, Thursday, 2 PM (Eastern Time), or let us know if that&apos;s not 

There is one JUnit failures that should be examined by owning teams
and confirmed explicitly if you want to declare with it or not.
(Its related to minor versioning problems -- would not effect validity of 

Current Build

Smoketest Results
wtp-releng mailing list

Back to the top