CndProcess

(Difference between revisions)
(Ideas)
(More unit tests)
 
(27 intermediate revisions not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
-
==CND Development Process Improvements==
+
==Issues==
-
 
+
-
===Issues===
+
# to hard to track regressions
# to hard to track regressions
# impossible to track tools compatibility
# impossible to track tools compatibility
-
===Solution===
 
-
# automated test system
 
-
=OLD=
+
==Solution==
-
===Rules===
+
===More unit tests===
-
# 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.
+
-
 
+
-
===Goals being solved===
+
-
# Improve predictability
+
-
# Have more time to stabilize release
+
-
# Early catches of design flaws, error prone code and other issues
+
-
# Better maintainability of our code base
+
-
# Early discovery of regressions
+
-
 
+
-
===Ideas===
+
{|- border="1"
{|- border="1"
-
! idea
+
|Identify most problematic areas
-
! status
+
|[[Media:CNDModulesStat.ods|Done]] (EU+VV)
|-
|-
-
| Introduce IDE static checks (AS: proposal)
+
|Introduce a goal for .next
 +
|TBD
|-
|-
-
| Code Style unification. As base we gonna use standard Java guideness. Someone volunteered to look for a tool to autocheck this.
+
|}
 +
 
 +
===Automated test system===
 +
{|- border="1"
 +
|involve different platforms
 +
|done
|-
|-
-
| Automated i18n checks
+
|introduce more convenient tests dashboard
-
| Done
+
|partly fixed (EU)
|-
|-
-
| Ask another NetBeans groups about their "best practices" for process (VV)
+
|track I18N warnings
 +
|done
|-
|-
-
| CND unit tests regularly/automatically
+
|static code checks
-
| Done
+
|done
|-
|-
-
| MORE unit tests
+
|review high priority FB warnings to introduce "zero rule" for them
-
| In progress
+
|
|-
|-
-
| More QA metrics and tests lovely presented in ICP
+
|get "blue build" (fix all tests on all platforms)
 +
|done (AS)
|-
|-
-
| Code Reviews
+
|current notifications are too distracting
 +
|fixed (AV)
|-
|-
-
| Design Reviews (schedules, specifications) -- as we tried at the beginning of last cycle but not really used.
+
|collect test coverage data
 +
|done (AV)
|-
|-
-
| We may have sandbox with different platform configurations to run unit tests there (AS)
+
|investigate which tools require compatibility testing
-
| Done
+
|
|}
|}
-
===Proposed rules to follow===
+
===General rules for developers===
-
====High priority====
+
* Compiler warnings highlighting and other hints in the IDE (Tools/Options/Editor/Hints) must be turned on
-
# we should have 0 "unevaluated" FindBugs warnings from "tracked" category (at the bottom of [[CndIncrementalBuilds| Incremental builds]])
+
* 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==
 +
# Improve predictability
 +
# Have more time to stabilize release
 +
# Early catches of design flaws, error prone code and other issues
 +
# Better maintainability of our code base
 +
# Early discovery of regressions
-
====Medium priority====
+
==Ideas==
-
# follow [http://java.sun.com/docs/codeconv/ Java Code Conventions], as soon as we have CheckStyle we should have 0 style warnings
+
* 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===
+
==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