CndProcess

Revision as of 11:22, 25 December 2009 by Gorrus (Talk | contribs)

Issues

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


Solution

More unit tests

Identify most problematic areas TBD
Introduce a goal for .next TBD

Automated test system

involve different platforms done
introduce more convenient tests dashboard
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 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