Archive for the ‘21123. Workflow’ Category.
10th June 2008, 09:17 pm
Below is the defect life cycle diagram.
Moreover, in “Defect Workflow for Mantis Bug Tracking System” topic, I described the defect workflow used by client, QA team, and Software Developer team in Mantis. In this piece, I improved the defect workflow aim to help client, QA team, and Software Developer team works and/or tasks further. The conformance to the defect workflow woould govern them to:
~ reduce the gaps due to lack of knowledge on the implied quality needs (specified in a project request and design, produced by the programmers, what the clients wanted) and/or approach governing the quality of their deliverables and products.
~ re-enforce Mantis;
~ optimize the current defect management process;
~ improve the quality of the deliverables;
~ improve team collaboration;
~ reduce errors or deficiencies in the process; and
~ prevent unforeseen problems.
The perceived benefits would be good service, lower development cost, and achieving the best possible results.
Join QAST Practitioner Group, download the material in MS Word version, and/or give comment(s) at: http://daniloalsonado.com/qastforum/index.php?topic=59.0
8th May 2008, 07:11 pm
In “Mantis - A Free Popular Web-based Bug Tracking System“ topic, it describes Mantis as free popular web-based bug tracking system. In this piece, it describes the defect workflow used by the QA Team and Dev Team in Mantis characteristically with the following activities:
1. Reporter - Reporting Issue Basics
2. QA Team - Reviewing
3. Reporter - Giving Feedback
4. Software Development Team - Reviewing
5. Software Developer - Marking Defect as Fixed
6. QA Team - Testing
7. QA Team - Acknowledging Defect for Closing
8. Reporter - User Acceptance Testing
9. Reporter - Closing Defect
Join QAST Practitioner Group, download the material in MS Word version, and/or give comment(s) at: http://daniloalsonado.com/qastforum/index.php?topic=59.0
26th April 2008, 11:54 pm
In “Template Content For Documenting Defects” topic, it describes how one can document the defects using a template for reporting defects, tracking defect status, and generating test summary report. This piece describes the defect workflow used in the template.
Note the defect workflow describes the repeatable pattern of activities, steps, and information in the defect reporting process and determines who is responsible for each activity or step to make the changes. It should be systematic and adaptable for managing and resolving defects.
Join QAST Practitioner Group, download the template and defect workflow material in MS Excel and Word version, and/or give comment(s) at:
http://daniloalsonado.com/qastforum/index.php?topic=58.0
