tests/integration/features/source_code_traceability/_language_parsers/c/08_c_static_definition_in_a_file/test.itest

Path:

Lines:

Non-empty lines:

Non-empty lines covered with requirements:

18 / 18 (100.0%)

Functions:

Functions covered by requirements:

0 / 0 (0.0%)

1 - 24 | entire file

"7.2.2. Language-aware parsing of C/C++ code" (REQUIREMENT)
"7.6.3. Language element marker" (REQUIREMENT)

SDOC-SRS-146

7.2.2. Language-aware parsing of C/C++ code

MID:

85a8080f8441485f9111ccda063b34bc

UID:

SDOC-SRS-146

STATUS:

Active

STATEMENT:

StrictDoc shall support parsing the C and C++ source files which includes:

- Recognizing functions and their Doxygen comments.
- Recognizing function declarations and function definitions.

RATIONALE:

C and C++ languages are common languages for embedded and general systems
programming. These languages have to be handled with a dedicated parser because
of these languages' specifics.

RELATIONS (File):

SDOC-SRS-137

7.6.3. Language element marker

MID:

61c23c1b106e4583b2c6d64bf1d296ba

UID:

SDOC-SRS-137

STATUS:

Active

STATEMENT:

StrictDoc shall support relation markers that can be attached to individual
source code elements. StrictDoc shall support an optional scope attribute to
disambiguate the target element where StrictDoc can't infer it solely from the
marker position.

Note: The most basic example of such traceable elements are functions and
classes, but generally supported elements and available scope attributes depend
on the programming language.

RATIONALE:

Source code elements can often be considered as the next level to trace from a
requirement. For example, a low level element is implemented by a function, or a
test case is implemented by a test function.

Sometimes it's also feasible to consider the source code elements as lean
replacement for prose requirement or test-case definitions.

RELATIONS (Parent):

SDOC-SSS-72 Traceability between requirements and source code

RELATIONS (Child):

SDOC-LLR-164 Auto-scoped relation markers in Rust docs

RELATIONS (File):

# @relation(SDOC-SRS-146, SDOC-SRS-137, scope=file)

RUN: %strictdoc export %S --output-dir %T | filecheck %s --dump-input=fail

CHECK: Published: Hello world doc

RUN: %check_exists --file "%T/html/_source_files/file.c.html"

RUN: %cat %T/html/%THIS_TEST_FOLDER/input.html | filecheck %s --check-prefix CHECK-HTML

CHECK-HTML: <a{{.*}}href="../_source_files/file.c.html#REQ-1#3#10">

CHECK-HTML: file.c, <i>lines: 3-10</i>, function hello_world_1

CHECK-HTML: <a{{.*}}href="../_source_files/file.c.html#REQ-2#12#19">

CHECK-HTML: file.c, <i>lines: 12-19</i>, function hello_world_2

RUN: %cat %T/html/_source_files/file.c.html | filecheck %s --check-prefix CHECK-SOURCE-FILE

CHECK-SOURCE-FILE: href="../_source_files/file.c.html#REQ-1#3#10"

CHECK-SOURCE-FILE: <b>[ 3-10 ]</b>

CHECK-SOURCE-FILE: file.c, function hello_world_1

CHECK-SOURCE-FILE: href="../_source_files/file.c.html#REQ-2#12#19"

CHECK-SOURCE-FILE: <b>[ 12-19 ]</b>

CHECK-SOURCE-FILE: file.c, function hello_world_2

RUN: %cat %T/html/source_coverage.html | filecheck %s --check-prefix CHECK-SOURCE-COVERAGE

CHECK-SOURCE-COVERAGE: 94.1

1 - 24 | entire file