#143 Add pattern for test.type
Opened 2 years ago by mvadkert. Modified 2 years ago

@@ -36,7 +36,7 @@ 

      "namespace": "baseos-qe.baseos-ci",

      "note": "Some notes.",

      "result": "failed",

-     "type": "tier1",

+     "type": "/test/tmt",

      "xunit": "https://somewhere.com/job/ci-openstack/4794/artifacts/results.xml"

    },

    "system":

file modified
+3 -1
@@ -100,8 +100,10 @@ 

              - pipeline

              - autocloud

              - base_selinux

-             - Any other identifier that makes sense for your test system

+             - /tmt/sanity

+             - install_default_update_live uefi updates-workstation-live-iso x86_64

          type: string

+         pattern: ^[a-zA-Z0-9/\-_\ ]+$

      scenario:

          description:

              Test scenario. Identifies scenario under which the test(s) are

It was raised to us we should be strict about what we
accept as test.type, so add an expected pattern to the
schema to make clear the expectations.

Next to it document a tmt like test type, which is used
in the wild for some time.

Signed-off-by: Miroslav Vadkerti mvadkert@redhat.com

ResultsDB does not fully support test case names with slashes / in names (backend API endpoint /api/v2.0/testcases and frontend links to backend are incorrect) - we are tracking the issue internally (RHELWF-7011 and RHELWF-7012).

Otherwise, LGTM. Can someone else review?