CndProcess

(Difference between revisions)
m (More unit tests)
(More unit tests)
 
(18 intermediate revisions not shown)
Line 3: Line 3:
# to hard to track regressions
# to hard to track regressions
# impossible to track tools compatibility
# impossible to track tools compatibility
 +
==Solution==
==Solution==
Line 8: Line 9:
{|- border="1"
{|- border="1"
|Identify most problematic areas
|Identify most problematic areas
-
|TBD
+
|[[Media:CNDModulesStat.ods|Done]] (EU+VV)
|-
|-
|Introduce a goal for .next
|Introduce a goal for .next
Line 17: Line 18:
===Automated test system===
===Automated test system===
{|- border="1"
{|- border="1"
-
! task
 
-
! status
 
-
|-
 
|involve different platforms
|involve different platforms
|done
|done
 +
|-
 +
|introduce more convenient tests dashboard
 +
|partly fixed (EU)
|-
|-
|track I18N warnings
|track I18N warnings
Line 33: Line 34:
|-
|-
|get "blue build" (fix all tests on all platforms)
|get "blue build" (fix all tests on all platforms)
-
|
+
|done (AS)
|-
|-
|current notifications are too distracting
|current notifications are too distracting
-
|fixing (AV)
+
|fixed (AV)
|-
|-
|collect test coverage data
|collect test coverage data
 +
|done (AV)
 +
|-
 +
|investigate which tools require compatibility testing
|
|
|}
|}
-
==Rules for developers==
+
===General rules for developers===
* 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.
Line 48: Line 52:
* 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===
+
 
 +
 
 +
=Obsolete=
 +
==Goals being solved==
# Improve predictability
# Improve predictability
# Have more time to stabilize release
# Have more time to stabilize release
Line 56: Line 63:
# Early discovery of regressions
# Early discovery of regressions
-
===Ideas===
+
==Ideas==
-
{|- border="1"
+
* Code Style unification. As base we gonna use standard Java guideness. Someone volunteered to look for a tool to autocheck this.
-
! idea
+
* More QA metrics and tests lovely presented in ICP
-
! status
+
* Code Reviews  
-
|-
+
* Design Reviews (schedules, specifications) -- as we tried at the beginning of last cycle but not really used.
-
| 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====
+
-
# we should have 0 "unevaluated" FindBugs warnings from "tracked" category (at the bottom of [[CndIncrementalBuilds| Incremental builds]])
+
-
 
+
-
====Medium priority====
+
-
# follow [http://java.sun.com/docs/codeconv/ Java Code Conventions], as soon as we have CheckStyle we should have 0 style warnings
+
-
===Links===
+
==Links==
[[CndIncrementalBuilds| Incremental builds]]
[[CndIncrementalBuilds| Incremental builds]]

Current revision as of 13:20, 2 February 2010

Issues

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


Solution

More unit tests

Identify most problematic areas Done (EU+VV)
Introduce a goal for .next TBD

Automated test system

involve different platforms done
introduce more convenient tests dashboard partly fixed (EU)
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) done (AS)
current notifications are too distracting fixed (AV)
collect test coverage data done (AV)
investigate which tools require compatibility testing

General 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.



Obsolete

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

  • Code Style unification. As base we gonna use standard Java guideness. Someone volunteered to look for a tool to autocheck this.
  • 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.

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