Forked from
tests / apertis-test-cases
621 commits behind the upstream repository.
-
Luis Araujo authoredThis commit addes a parser for the test case format, so it can detect the most common mistakes (missing field or incorrect types for values) in the test case yaml file. This commit also adds a few more ported test cases. Signed-off-by:
Luis Araujo <luis.araujo@collabora.co.uk>Luis Araujo authoredThis commit addes a parser for the test case format, so it can detect the most common mistakes (missing field or incorrect types for values) in the test case yaml file. This commit also adds a few more ported test cases. Signed-off-by:Luis Araujo <luis.araujo@collabora.co.uk>
format_template.yaml 760 B
metadata:
name:
format: "Apertis Test Definition 1.0"
# [ target, minimal, ostree, development, SDK, any ].
image-type:
# [ amd64, arm64, armhf, any ]
image-arch:
# [ functional, sanity, system ]
type:
# [ manual , automated ]
exec-type:
# [ low, medium, high, critical ]
priority:
maintainer: "Apertis Project"
description:
resources:
pre-conditions:
expected:
notes:
post-conditions:
# Only valid for automated non-ostree images installing packages.
install:
deps:
run:
steps:
# Parse test results from the test command output.
# This directive is only relevant for LAVA automated tests.
parse:
fixupdict:
FAILED: fail
PASSED: pass
pattern: '(?P<test_case_id>[^:]+): (?P<result>[A-Z]+)'