Is it based on the no of bugs existing in your product? If so, how can we prepare our product to make it bug free or releasable.
Do you collect bug reports for you project? Then how often do you do?
Bug reports are important for any software development. It is a good practice to collect bug reports. In our company, this is one of the good practices we follow, collecting bug reports.
Collecting bug reports helps both development and quality teams to track down and fix bugs in product. These reports improves the quality of final product. They helps to prepare product launch. Until all the P0, P1 and P2 defects are fixed, the project is not ready to ship.
The analysis of the data collected helps in understanding more about a particular set of problems or tests. Also helps in understanding and reporting the overall level of quality.
Finally, defect reports, when analyzed over a product/project and even across projects, give information that can lead to development and test process improvements.
Do you collect bug reports for you project? Then how often do you do?
Bug reports are important for any software development. It is a good practice to collect bug reports. In our company, this is one of the good practices we follow, collecting bug reports.
Collecting bug reports helps both development and quality teams to track down and fix bugs in product. These reports improves the quality of final product. They helps to prepare product launch. Until all the P0, P1 and P2 defects are fixed, the project is not ready to ship.
The analysis of the data collected helps in understanding more about a particular set of problems or tests. Also helps in understanding and reporting the overall level of quality.
Finally, defect reports, when analyzed over a product/project and even across projects, give information that can lead to development and test process improvements.
No comments:
Post a Comment