[Meego-qa] questions about "Verified" and "Closed" status in feature lifecycle
elva.fu at intel.com
Mon May 16 17:54:26 PDT 2011
How about we discuss a little in next IRC QA meeting? :)
From: meego-qa-bounces at lists.meego.com [mailto:meego-qa-bounces at lists.meego.com] On Behalf Of Fu, Elva
Sent: Saturday, May 14, 2011 12:16 PM
To: meego-qa at lists.meego.com
Subject: [Meego-qa] questions about "Verified" and "Closed" status in feature lifecycle
Seems there are some discrepancy within https://meego.com/developers/requirements. In the first picture, "Verified" is defined as "No bugs related to this Feature", however in the second picture, if "No bugs linked to this feature" the status will be "Closed", so what the status will be if no bugs for this feature? :)
"Once a requirement is integrated, MeeGo QA verifies it by running the corresponding test cases. Bugs are filed against the requirements and marked with a dependency. Eventually, once there are no longer bugs preventing closing the feature, it is closed in Featurezilla" is mentioned in this page. but as far as I know, if an Open bug is linked to a feature(depend on field), bugzilla does not allow people to change status to Verified, so seems QA is unable to follow the process to verify and link Open bugs at the same time. According to our practice, how about we change the process like that:
* If the feature meets the intent of the requirement, QA will set status to Verified.
* If the feature Basically meets the intent of the requirement(e.g. passed Basic functionality testing and no critical&major bug found), QA will set status to Verified. At the same time, QA will add comment to indicate there are small bugs(if any) for this feature.
* QA set status to Reopened if the feature has a lack of functionality it was intended to have. QA will file bug and Link the bug to this feature.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MeeGo-qa