Difference between revisions of "WTP Smoke Test Results R313"
(Created page with "This is a blank template page to be used to create new Smoke Test pages. Just copy it to a new URL, and voila! Fresh smoked page. == Smoke Test Promotion votes == Instructio...") |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 12: | Line 12: | ||
so those doing the promotion know its ready to go. | so those doing the promotion know its ready to go. | ||
| − | If a | + | If a '''[[WTP Smoke Test Scenarios|Smoke Test]]''' does not pass but the build can still be |
promoted, use a green check mark (ok) icon ([[Image:Checkmark.gif]]) but then | promoted, use a green check mark (ok) icon ([[Image:Checkmark.gif]]) but then | ||
document in the comments bug numbers, how the smoke test fails, workarounds, | document in the comments bug numbers, how the smoke test fails, workarounds, | ||
| Line 30: | Line 30: | ||
Keep in mind the threshold for promoting a build | Keep in mind the threshold for promoting a build | ||
gets higher as we near a milestone or near a release. | gets higher as we near a milestone or near a release. | ||
| + | |||
| + | '''PLEASE REMEMBER TO USE JDK 11 and 8, as we support both.''' | ||
{| border="3" cellpadding="5" | {| border="3" cellpadding="5" | ||
Latest revision as of 17:09, 21 February 2019
This is a blank template page to be used to create new Smoke Test pages. Just copy it to a new URL, and voila! Fresh smoked page.
Smoke Test Promotion votes
Instructions:
Use a red X (fail) icon (
) to signify that the
build should not be promoted, that a respin is required. In that case, please
provide bug number and be sure those that need to fix something are aware of it,
and can arrange for a respin. Once the issue has been fixed, and confirmed,
change the red X to a green check mark with the build Id where is was verified,
so those doing the promotion know its ready to go.
If a Smoke Test does not pass but the build can still be
promoted, use a green check mark (ok) icon (
) but then
document in the comments bug numbers, how the smoke test fails, workarounds,
or cautions about the build.
If a build can be promoted and no issues were found, simple use the green check mark and include the initials or names of who performed the test.
Remember the significant column for promoting a build is the left-most project column. If some component within a project has not (or can not) be tested, the Project Lead should either make sure someone does the test, or make a judgment call on if the build (from their project's point of view) can be promoted or not. If the smoke test could not be performed, a note should be made in the comments section that it wasn't performed, why, and why that should prevent promotion.
Keep in mind the threshold for promoting a build gets higher as we near a milestone or near a release.
PLEASE REMEMBER TO USE JDK 11 and 8, as we support both.
| Project | Vote | Initials Comments
|
| Java EE | 
|
DG |
| JSF |
|
IMT |
| Dali |
|
njh |
| Server |
|
SC |
| Web Services, WSDL |
|
Web Services (kc)
|
| JSDT,
Node.js tools (bower, npm, grunt, gulp) |
|
JSDT (vr)
|
| Source Editing |
|
XML + JSP (vr)
|
| Release Engineering |
|
nb |
Smoke Test ok to promote vote =Smoke Test do not promote vote =
Smoke Test Pending =
