Howdy all, We're going to try something new in the Product Team: daily exploratory testing.
The idea is this: the sooner we test something, the sooner we catch any problems and the more chance we get of fixing them before they go live. So, here's what we're going to do. Starting Monday and for four weeks, Diogo will test every feature branch that lands. Towards the end of a feature's development cycle, he'll also do another round of exploratory testing on the feature as a whole. He'll be looking for the same problems he does when conducting exploratory testing towards the end of a feature's cycle. However, this will also offer a second chance to catch any issues that might block a roll-out. This doesn't change the normal QA that everyone does: please still QA your own branches as normal. The outputs will be: mostly High bugs and, on occasion, a Critical bug along with a qa-bad tag. Why only feature branches? Diogo still has other work to do (such as OOPS checking and whole feature testing) so we chose to limit the burden this would put on Diogo during this experiment. As feature branches are more likely to introduce new stuff, and the level of landings looked workable to Diogo, we settled on feature branches. I think there's a case to also cover branches related to escalated bugs but we'll see how the experiment goes with feature branches first. Any comments? -- Matthew Revell Launchpad Product Manager Canonical https://launchpad.net/~matthew.revell _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
