Difference between revisions of "WTP Smoke Test Results R380 03102016"
(Created page with "== Smoke Test Promotion votes == Instructions: Use a red X (fail) icon (Image:Fail.gif) to signify that the build should not be promoted, that a respin is required. In...")
(→Smoke Test Promotion votes)
|Line 39:||Line 39:|
| align="center" |[[Image:
| align="center" |[[Image:.gif]]
Revision as of 16:02, 10 March 2016
Smoke Test Promotion votes
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.
|Web Services, WSDL||Web Services|
Node.js tools (bower, npm, grunt, gulp)
|Source Editing||XML + JSP|