User Tools

Site Tools


workgroup:codequality:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
workgroup:codequality:start [2017/04/20 04:02]
Daniel Agar
workgroup:codequality:start [2017/07/27 20:43] (current)
Mark Charlebois
Line 8: Line 8:
   * Coverity - https://​scan.coverity.com/​projects/​px4-firmware   * Coverity - https://​scan.coverity.com/​projects/​px4-firmware
   * clang-tidy   * clang-tidy
-  * astyle - consistent code formatting improves readability and reduces potential merge conflicts for downstream adopters.+  * astyle - consistent code formatting improves readability and reduces potential merge conflicts for downstream adopters 
 +  * Docker - consistent, repeatable build environment
  
  
Line 23: Line 24:
   * mission tests   * mission tests
   * unit tests   * unit tests
- +  * SITL (Software in the loop) 
 +  * HIL (Hardware in the loop)
  
 __Todo__ __Todo__
Line 33: Line 34:
   * hardware tests   * hardware tests
   * perf tracking   * perf tracking
 +  * Automated testing (static analysis, etc)
 +  * Running with address sanitier and thread sanitizer enabled
 +  * Clang tidy expand usage (modernize c++)
 +  * Identifying code in desperate need of refactoring (commander)
 +  * Using safe C++ types
 +     * A time in ms should be a time_ms type vs an int, safe addition, multiplication can then be used
 +     * Convert Orb and param usage to C++ APIs for type safety
 +  * Commander re-write
 +  * Better quantified code coverage tests
 +  * Make it easier for people to contribute and maintain code quality
 +  * Unify NuttX and DriverFramework drivers
 +    * Create design pattern for driver based on cross platform requirements
 +
  
workgroup/codequality/start.1492660946.txt.gz · Last modified: 2017/04/20 04:02 by Daniel Agar