From ea35ff14c7467519a7c3d671f0d8cac79f342902 Mon Sep 17 00:00:00 2001 From: marblom007 <158522975+marblom007@users.noreply.github.com> Date: Sun, 2 Aug 2026 23:16:15 -0500 Subject: [PATCH 1/2] [QA] Rename connections report to "Meshery: Connections Lifecycle" Rename the `connections` awesome-plugin report's display name to "Meshery: Connections Lifecycle" and decouple that display name from the testGroup filter key. Previously one constant (CONNECTION_LIFECYCLE_GROUP) drove both the reportName and the isTestGroup filter, so the two could not be renamed independently. Split out CONNECTION_REPORT_NAME for the display name; the filter still keys on the "Connection Lifecycle" testGroup value the tests emit, so the match is unchanged. The plugin key stays `connections`, so the published URL (https://qa.meshery.io/connections/) is unchanged. Nesting: the "Meshery: " prefix presents this as a Meshery report in the dashboard's report picker. Allure 3 reports are flat peer plugins (the config `plugins` map has no parent/child relation; the awesome plugin's only hierarchy is intra-report groupBy), so a name prefix is the supported way to signal that this report is a subset of the main Meshery report - documented inline. Signed-off-by: marblom007 <158522975+marblom007@users.noreply.github.com> --- allurerc.mjs | 30 +++++++++++++++++++++++++----- 1 file changed, 25 insertions(+), 5 deletions(-) diff --git a/allurerc.mjs b/allurerc.mjs index 20cf787ec33..2f3e46b86b5 100644 --- a/allurerc.mjs +++ b/allurerc.mjs @@ -26,11 +26,22 @@ const isTestGroup = (labels, groupName) => const hasTestGroup = (labels) => labels.some(({ name }) => name === "testGroup"); -// Single source of truth for the Connection Lifecycle Test Group value - used -// for both the report display name and the testGroup filter so the two cannot -// drift apart. +// The Connection Lifecycle Test Group VALUE - this is the `testGroup` label +// value the tests emit (Test Plan "Latest" tab, col B), so it is the report's +// FILTER key and MUST match the value tagged at the source (UI specs + CLI +// converter). Do NOT change it to rename the report - the display name is a +// separate constant below. const CONNECTION_LIFECYCLE_GROUP = "Connection Lifecycle"; +// The connection report's DISPLAY name, decoupled from the filter key above so +// the report can be renamed without breaking the testGroup match. The +// "Meshery: " prefix presents it as a Meshery report in the dashboard's report +// picker (lightweight nesting under the main Meshery report) - Allure 3 reports +// are flat peer plugins with no parent/child nesting in the config, so the +// prefix is the supported way to signal the relationship. See the connections +// plugin block below. +const CONNECTION_REPORT_NAME = "Meshery: Connections Lifecycle"; + // --- Transitional epic-based fallback (remove once all connection results // carry testGroup) ----------------------------------------------------------- // Before this rename the connection report keyed on epic="Kubernetes @@ -155,7 +166,16 @@ export default defineConfig({ // // The plugin key stays `connections` so the published report URL // (https://qa.meshery.io/connections/) is unchanged; only the display name - // and filter change. + // changes (reportName = CONNECTION_REPORT_NAME, "Meshery: Connections + // Lifecycle"). The filter (isTestGroup "Connection Lifecycle") is unchanged. + // + // Nesting: the "Meshery: " prefix presents this as a Meshery report in the + // dashboard's report picker. Allure 3 reports are flat peer plugins (the + // config `plugins` map has no parent/child relation, and the awesome + // plugin's only hierarchy is intra-report `groupBy`), so a name prefix is + // the supported way to signal that this is a subset of the main Meshery + // report; true report-under-report nesting is not available without folding + // these results into the Meshery report and losing the standalone URL. // // Transitional: the isConnectionBehavior (epic) fallback keeps the report // populated with connection results emitted before the testGroup label @@ -167,7 +187,7 @@ export default defineConfig({ connections: { import: "@allurereport/plugin-awesome", options: { - reportName: CONNECTION_LIFECYCLE_GROUP, + reportName: CONNECTION_REPORT_NAME, singleFile: false, reportLanguage: "en", open: false, From 9057a97ef4ac53573b3644ff8c3a646aafd20c45 Mon Sep 17 00:00:00 2001 From: marblom007 <158522975+marblom007@users.noreply.github.com> Date: Sun, 2 Aug 2026 23:25:14 -0500 Subject: [PATCH 2/2] [QA] De-duplicate the nesting rationale comment Address review (Copilot): the '"Meshery: "' prefix / flat-reports rationale was explained on the CONNECTION_REPORT_NAME constant and repeated in the connections plugin block. Keep the full rationale only in the plugin block (where reportName is used) and leave a short pointer on the constant, so the two cannot drift. Signed-off-by: marblom007 <158522975+marblom007@users.noreply.github.com> --- allurerc.mjs | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/allurerc.mjs b/allurerc.mjs index 2f3e46b86b5..b4693266c86 100644 --- a/allurerc.mjs +++ b/allurerc.mjs @@ -35,11 +35,8 @@ const CONNECTION_LIFECYCLE_GROUP = "Connection Lifecycle"; // The connection report's DISPLAY name, decoupled from the filter key above so // the report can be renamed without breaking the testGroup match. The -// "Meshery: " prefix presents it as a Meshery report in the dashboard's report -// picker (lightweight nesting under the main Meshery report) - Allure 3 reports -// are flat peer plugins with no parent/child nesting in the config, so the -// prefix is the supported way to signal the relationship. See the connections -// plugin block below. +// "Meshery: " prefix is intentional - see the connections plugin block below +// for the nesting rationale (kept in one place to avoid drift). const CONNECTION_REPORT_NAME = "Meshery: Connections Lifecycle"; // --- Transitional epic-based fallback (remove once all connection results