| ... | ... | @@ -273,7 +273,7 @@ Important rules, and notable differences are summarized here: |
|
|
|
|
|
|
|
- Test your code with ```-pedantic``` compiler flag enabled.
|
|
|
|
- Warnings have to be fixed, when they appear on the system(s) currently used by the CI, by altering the code unless the warning originates from third-party code and cannot be fixed. In such cases, developers of the third-party project should be informed. Should the warning be locally silenced, either using appropriate pragmas or locally turning off warnings for that translation unit, documentation should be added in the entry point triggering the
|
|
|
|
warning using the flag ```"FIXME"```.
|
|
|
|
warning using the flag ```"FIXME"``` as keyword.
|
|
|
|
- All unit tests must succeed on the specified systems/configurations on gitlab-ci. If tests fail, code is not merged. In certain cases, core developing team will consider to update or extend the CI systems.
|
|
|
|
- The unit test code coverage should never decrease due to a new merge request.
|
|
|
|
- Exceptions and error handling
|
| ... | ... | |
