Hi all, I'm Nicolas Paccou from Intel France QA in Montpellier. Since several weeks, I work on oFono features (Classification: MeeGo Features - Component: Telephony) and I use Bugzilla (http://bugs.meego.com<https://bugs.meego.com>) every day to follow them. I have noticed several issues that makes difficult/slows down my work. I request your help in order to find a solution to solve them.
Please find below the first issue that is related to Bugzilla itself. I wonder if there is a way to ameliorate the situation on this ? 1. [MASTER] features are not systematically created to regroup features of a components. Without this hierarchy between features, the visibility on what major features are included in a component is confused. e.g.: no master feature to regroup all Cell Broadcast features in oFono Please find below several points where the process is not (correctly) applied. Please help me to find a way to avoid this kind of application: 2. Feature description is often not enough detailed to be able to write test cases. QA loses lots of time to clarify each feature in order to review the testability. e.g.: Feature 4677<https://bugs.meego.com/show_bug.cgi?id=4677> - [FEA] Cellular - 2G PS Data Profile Settings (where description is just missing !) 3. Often not the real Feature Assignee and QA Contact own a feature which does not facilitate the feature understanding. Often Manager are assigned to a feature and do not always forward request/questions to real feature/QA owner which makes lose precious time. e.g.: Feature 4677<https://bugs.meego.com/show_bug.cgi?id=4677> - [FEA] Cellular - 2G PS Data Profile Settings (where Feature Assignee is not the real feature owner but a manager) 4. Often no answer when posting a testability review or a simple question/request on the feature. This can be linked to issue 3 (not the good person owns the feature). E.g.: Feature 4490<https://bugs.meego.com/show_bug.cgi?id=4490> - [FEA] Cellular - SATK - Refresh (no feedback on testability review) 5. Process is often not applied: - Wrong status for a feature (e.g.: VERIFIED or RESOLVED instead of RELEASED) - Often no testability review (e.g.: Testability field set to "Yes" or "No" without reason) - Often no comment to justify a change of status (e.g.: from ACCEPETED to REJECTED or from INDEFINITION to ACCEPTED) Again, could you help me to find a solution to the problem above please ? Best regards, ________________________ Nicolas Paccou Test Engineer [cid:image001.png@01CC08D0.FC596AC0]SSG INTEL Corp. Montpellier, France Soft Phone: 8 665 1031 nicolas.pac...@intel.com --------------------------------------------------------------------- Intel Corporation SAS (French simplified joint stock company) Registered headquarters: "Les Montalets"- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 4,572,000 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
<<inline: image001.png>>
_______________________________________________ MeeGo-qa mailing list MeeGo-qa@lists.meego.com http://lists.meego.com/listinfo/meego-qa
