CndProcess

(Difference between revisions)
(CND Development Process Improvements)
Line 1: Line 1:
__NOTOC__
__NOTOC__
-
 
==Issues==
==Issues==
# to hard to track regressions
# to hard to track regressions
Line 6: Line 5:
==Solution==
==Solution==
-
 
+
===More unit tests===
-
===more unit tests===
+
{|- border="1"
{|- border="1"
! task
! task
Line 14: Line 12:
|Identify most problematic areas
|Identify most problematic areas
|
|
 +
|-
 +
|Introduce a goal for .next
 +
|
 +
|-
|}
|}
-
 
+
===Automated test system===
-
===automated test system===
+
{|- border="1"
{|- border="1"
! task
! task
Line 30: Line 31:
|done
|done
|-
|-
-
|get to zero (fix all tests on all platforms)
+
|review high priority FB warnings to introduce "zero rule" for them
 +
|
 +
|-
 +
|get "blue build" (fix all tests on all platforms)
|
|
|-
|-
Line 40: Line 44:
|}
|}
-
=OLD=
+
==Rules for developers==
-
===Rules===
+
* Compiler warnings highlighting and other hints in the IDE (Tools/Options/Editor/Hints) must be turned on
-
# Compiler warnings highlighting and other hints in the IDE (Tools/Options/Editor/Hints) must be turned on
+
* Deprecation compiler warnings must be fixed asap or filed as P2 bugs.
-
# Deprecation compiler warnings must be fixed asap or filed as P2 bugs.
+
* "Unchecked" compiler warnings must be fixed asap or filed as P2 bugs. (@SuppressWarnings("unchecked") should only be used with extra comment)
-
# "Unchecked" compiler warnings must be fixed asap or filed as P2 bugs. (@SuppressWarnings("unchecked") should only be used with extra comment)
+
* I18n warnings must be fixed asap or filed as P2 bugs.
-
# I18n warnings must be fixed asap or filed as P2 bugs.
+
 +
=OLD=
===Goals being solved===
===Goals being solved===
# Improve predictability
# Improve predictability

Revision as of 14:45, 8 December 2009

Issues

  1. to hard to track regressions
  2. impossible to track tools compatibility

Solution

More unit tests

task status
Identify most problematic areas
Introduce a goal for .next

Automated test system

task status
involve different platforms done
track I18N warnings done
static code checks done
review high priority FB warnings to introduce "zero rule" for them
get "blue build" (fix all tests on all platforms)
current notifications are too distracting fixing (AV)
collect test coverage data

Rules for developers

  • Compiler warnings highlighting and other hints in the IDE (Tools/Options/Editor/Hints) must be turned on
  • Deprecation compiler warnings must be fixed asap or filed as P2 bugs.
  • "Unchecked" compiler warnings must be fixed asap or filed as P2 bugs. (@SuppressWarnings("unchecked") should only be used with extra comment)
  • I18n warnings must be fixed asap or filed as P2 bugs.

OLD

Goals being solved

  1. Improve predictability
  2. Have more time to stabilize release
  3. Early catches of design flaws, error prone code and other issues
  4. Better maintainability of our code base
  5. Early discovery of regressions

Ideas

idea status
Code Style unification. As base we gonna use standard Java guideness. Someone volunteered to look for a tool to autocheck this.
Ask another NetBeans groups about their "best practices" for process (VV)
More QA metrics and tests lovely presented in ICP
Code Reviews
Design Reviews (schedules, specifications) -- as we tried at the beginning of last cycle but not really used.

Proposed rules to follow

High priority

  1. we should have 0 "unevaluated" FindBugs warnings from "tracked" category (at the bottom of Incremental builds)

Medium priority

  1. follow Java Code Conventions, as soon as we have CheckStyle we should have 0 style warnings

Links

Incremental builds

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo