We should adhere to Dasharo naming conventions in tests #991
Description
OSFV version
Affected component(s) or functionality
DTS E2E tests.
Expected behavior
We should adhere to https://docs.dasharo.com/dasharo-naming-convention/ . E.g.:
diff --git a/platform-configs/include/default.robot b/platform-configs/include/default.robot
index 9ef99f56b6e8..599aea767e85 100644
--- a/platform-configs/include/default.robot
+++ b/platform-configs/include/default.robot
@@ -399,6 +399,7 @@ ${DTS_TEST_VERSION_BASE}= v0.0.0
... &{{ {workflow: "${DTS_TEST_VERSION_BASE}" for workflow in ${DTS_TEST_POSSIBLE_WORKFLOWS} } }}
... UEFI Update=Dasharo (coreboot+UEFI) ${DTS_TEST_VERSION_BASE}
... UEFI->Heads Transition=Dasharo (coreboot+UEFI) ${DTS_TEST_VERSION_BASE}
+... Dasharo (coreboot+UEFI)->Dasharo (Slim Bootloader+UEFI) Transition=Dasharo (coreboot+UEFI) ${DTS_TEST_VERSION_BASE}
&{DTS_TEST_VERSIONS}= &{DTS_TEST_VERSIONS_BASE}
# TEST_SYSTEM_MODEL, TEST_BOARD_MODEL, TEST_SYSTEM_VENDOR variables to export
Actual behavior
&{DTS_TEST_VERSIONS_BASE}=
... &{{ {workflow: "${DTS_TEST_VERSION_BASE}" for workflow in ${DTS_TEST_POSSIBLE_WORKFLOWS} } }}
... UEFI Update=Dasharo (coreboot+UEFI) ${DTS_TEST_VERSION_BASE}
... UEFI->Heads Transition=Dasharo (coreboot+UEFI) ${DTS_TEST_VERSION_BASE}
... Dasharo (coreboot+UEFI)->Dasharo (Slim Bootloader+UEFI) Transition=Dasharo (coreboot+UEFI) ${DTS_TEST_VERSION_BASE}Additional context
Note, that the tests do not need the [customer_type] Package for market_segment field. It only uses the Dasharo (firmware_framework[+payload]) + the DCR or DPP that signal the access type.