Difference between revisions of "WTP Quality"

From Eclipsepedia

Jump to: navigation, search
(New page: ==Thoughts on quality for the Web Tools Project== ===How do we ensure quality in the WTP Project?=== *'''High committer standards''' **More than anything else, high quality committers wil...)
 
(Related Bug Reports)
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Thoughts on quality for the Web Tools Project==
+
==Thoughts on Quality for the Web Tools Project (Work In Progress)==
 +
This wiki page should describe how the WTP addresses the issue of Quality.
  
 
===How do we ensure quality in the WTP Project?===
 
===How do we ensure quality in the WTP Project?===
Line 5: Line 6:
 
**More than anything else, high quality committers will result in high quality software
 
**More than anything else, high quality committers will result in high quality software
 
*'''Adequate JUnit tests for components'''
 
*'''Adequate JUnit tests for components'''
**Necessary for early bug detection in the lifecycle and future maintainability of the software
+
**Necessary for early bug detection in the development life-cycle and future maintainability of the software
 
*'''Continuous and Integration Builds'''
 
*'''Continuous and Integration Builds'''
*'''Releasing early in the dev cycle at predictable intervals'''
+
*'''Releasing early in the development life-cycle at predictable intervals'''
 +
**Among other things, this allows users to test functionality and find bugs before the software is released
 
*'''Focus on bug reports'''
 
*'''Focus on bug reports'''
**Ensure that meaningful bugs from the community are addressed in a reasonable time period
+
**Ensure that important bugs from the community are addressed in a reasonable time period
**This is where the community can have an impact on the overall quality of the project through both entering bugs and by fixing them
+
**This is another place where the community can have an impact on the overall quality of the project through both entering bugs and by fixing them
 
+
  
 
===Related Bug Reports===
 
===Related Bug Reports===
[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Total Bugs by Severity]
+
 
 +
*[https://bugs.eclipse.org/bugs/reports.cgi?product=Web+Tools&datasets=NEW%3A&datasets=ASSIGNED%3A&datasets=REOPENED%3A&datasets=CLOSED%3A&datasets=FIXED%3A Overall Bug Health Chart]
 +
*[https://bugs.eclipse.org/bugs/reports.cgi?product=Web+Tools&datasets=NEW%3A&datasets=ASSIGNED%3A&datasets=REOPENED%3A Focus on New/Open bugs]
 +
 
 +
*[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Total Bugs by Severity]
 +
 
 +
*[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&target_milestone=2.0+M1&target_milestone=2.0&target_milestone=2.0+M2&target_milestone=2.0+M3&target_milestone=2.0+M4&target_milestone=2.0+M5&target_milestone=2.0+M6&target_milestone=2.0+RC1&target_milestone=2.0+M7&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= 2.0 Total Bugs Fixed]
 +
 
 +
*[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_severity&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Dali+JPA+Tools&target_milestone=1.0+M5&target_milestone=1.0+M6&target_milestone=1.0+RC1&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= 2.0 JPA Total Bugs Fixed]
 +
 
 +
 
 +
 
 +
 
 +
 
 +
[[Category:Eclipse Web Tools Platform Project]]

Latest revision as of 14:36, 5 February 2008

[edit] Thoughts on Quality for the Web Tools Project (Work In Progress)

This wiki page should describe how the WTP addresses the issue of Quality.

[edit] How do we ensure quality in the WTP Project?

  • High committer standards
    • More than anything else, high quality committers will result in high quality software
  • Adequate JUnit tests for components
    • Necessary for early bug detection in the development life-cycle and future maintainability of the software
  • Continuous and Integration Builds
  • Releasing early in the development life-cycle at predictable intervals
    • Among other things, this allows users to test functionality and find bugs before the software is released
  • Focus on bug reports
    • Ensure that important bugs from the community are addressed in a reasonable time period
    • This is another place where the community can have an impact on the overall quality of the project through both entering bugs and by fixing them

[edit] Related Bug Reports