CndProcess
Issues
- to hard to track regressions
- impossible to track tools compatibility
Solution
More unit tests
Identify most problematic areas | File:CNDModulesStat.ods (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
- 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
- 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.