<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Hi,</div><div><br></div><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div><br></div><div>QE is almost done qualifying MS5 ... so I thought I would share information at this intermediary point. The link is to a mojo page which summarizes QE activities and findings. </div><div><br></div><div><br class="Apple-interchange-newline"><span style="color: #0000ee; text-decoration: underline;" data-mce-style="color: #0000ee; text-decoration: underline;">https://mojo.redhat.com/docs/DOC-1047356</span></div><div><br></div><div>The highlights are:</div><div><ul><li>UI Automation. New tests added for every JMAN4 Jira delivered. Regression testing on previously delivered Jiras. All results stored in Polarion. All links to pull requests for the creation and refactoring of UI automation.</li><li>REST API automation. New tests added for every JMAN4 Jira delivered. Regression testing on previously delivered Jiras. All results stored in Polarion. All links to pull requests for the creation and refactoring of REST API automation.</li><li>Performance CI on Hawk-Metrics. Throughput, response time, and disk usage for every pull request, with a goal to catch performance regressions as they happen. All results stored in Perf Repo.</li><li>Manual testcases. New documented testcases for every JMAN4 delivered in MS5. Documented testcase execution with results stored in Polarion.</li><li>Continuous Delivery Pipeline. Hawkular is containerized, a smaller suite of REST API tests are run, and if successful then pushed to a public facing endpoint. <a href="http://livingontheedge.hawkular.org/" target="_blank">http://livingontheedge.hawkular.org/</a><br></li><li>Jiras logged for every issue found as a result of these activities. </li></ul><div><br></div><div><br></div><div>We are planning on reviewing the testing activities next Thursday October 15th. Please, you are invited to review, listen, ask questions on this testing ... or even influence or contribute to testing on the next sprint. Please feel free to contact me if you have questions, comments, or suggestions regarding this testing.</div><div><br></div><div>Regards,</div><div><br></div><div>Michael Foley</div><div>QE Supervisor, Middleware BU </div></div><div><br></div><div><br></div><div><br></div><div><br></div></div></div></div></body></html>