diff options
Diffstat (limited to 'spec/req/unit-test-dead-code.yml')
| -rw-r--r-- | spec/req/unit-test-dead-code.yml | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/spec/req/unit-test-dead-code.yml b/spec/req/unit-test-dead-code.yml new file mode 100644 index 00000000..57961d16 --- /dev/null +++ b/spec/req/unit-test-dead-code.yml @@ -0,0 +1,19 @@ +SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause +copyrights: +- Copyright (C) 2022 embedded brains GmbH (http://www.embedded-brains.de +enabled-by: true +links: +- role: requirement-refinement + uid: root +non-functional-type: design +rationale: | + In general, dead code should be avoided. For justified exceptions it is + acceptable, for example to avoid hard to maintain deviations from the RTEMS + mainline code. For these exceptions, unit tests may be used to achieve the + code and branch coverage goals. +references: [] +requirement-type: non-functional +text: | + Unit tests may be used to test code which is not testable through the + ${/glossary/api:/term}. +type: requirement |