tests: cleanup: Explain the purpose of some tests
authorErica Bugden <ebugden@efficios.com>
Fri, 5 May 2023 17:37:00 +0000 (13:37 -0400)
committerErica Bugden <ebugden@efficios.com>
Wed, 31 May 2023 15:19:34 +0000 (11:19 -0400)
commit0ea3b42940513043afa1f8c2e75627f479e1b1d7
tree64d30fd85cb0834d2f691caca696e890bab400bb
parentb2fd4fd81d6da66463c4ecf1f7798bfda8f873f4
tests: cleanup: Explain the purpose of some tests

Tests explained:
    * test_everything() (see note below)
    * `include` test cases

Identifying the intended purpose of the `include` test cases is a
partial prerequisite for the future work of checking that each
configuration test expecting a failure fails for the intended reason. At
the momment, we only check that configuration fails regardless of the
reason.

Note: test_everything() is a single stand alone test case that dates
back to from barectf 2 before the `tracing` tests existed. This is why
it checks more than just configuration generation. It is possibly
redundant with the more extensive tracing tests.

Change-Id: I59fe258b4f1eb7ef5c83f717f12973d38269adb4
Signed-off-by: Erica Bugden <ebugden@efficios.com>
tests/config/yaml/2/configs/fail/include/cycle.yaml
tests/config/yaml/2/configs/fail/include/file-not-found-abs.yaml
tests/config/yaml/2/configs/fail/include/file-not-found-in-array.yaml
tests/config/yaml/2/configs/fail/include/file-not-found-recursive.yaml
tests/config/yaml/2/test_pass_everything.py
This page took 0.023759 seconds and 4 git commands to generate.