/projects/blog/archive/2007_07_18_archive.php (jwalsh.net)

Tech notes, bookmarks, and misc. notes

archives

Wednesday, July 18, 2007

The following can be used for the Process Dashboard Manage Defect Type Standards updates for a better reflection of WebDev projects:

10 Documentation (documents, comments, or messages)
20 Syntax (a defect generally found by the JSP compiler)
30 Build (errors in version control or in change management)
40 Layout (non-conformance to the design)
50 Interface (invalid use of includes for JSP, CSS, or JavaScript)
60 Checking (missing, wrong, or inadequate handling of error cases)
70 Data (amount of data prevented a particular case from being seen)
80 Function (defects beyond one statement in algorithms or functionality)
90 System (configuration management, ad serving, databases, network, or hardware)
100 Environment (defect in development environment or support systems)

posted by j 7/18/2007 02:35:00 PM

review_process Originally uploaded by jwalsh

Purpose

Create a simple tracking mechanism for performing code reviews against CVS.

Use Case

Identify current project
Identify review cycle
Identify reviewer
Review specific files in CVSWeb through an annotate view
Click add review for specific line in annotate for the code in scope
During review, go through each of the comments
Add a resolution and comment to close a review item
If no items are open, close the current review cycle

Application

Rails connecting to a database with projects, reviewers, cycles, and reviews tables. reviews will have id, filename, revision, line, comment, outcome, resolution, project_id, reviewer_id, and cycle_id.

Code will be available in http://wal.sh/code/reviewer/trunk/.

posted by j 7/18/2007 12:33:00 PM