Dashboards on qa.meshery.io

17 views
Skip to first unread message

marcus ringblom

unread,
Aug 3, 2026, 1:52:10 AM (yesterday) Aug 3
to Meshery Developers
Hi All,

A few of us have spent time updating the Meshery Test Plan spreadsheet with about 80 new test cases under a new test group, “Connection Lifecycle”. 

Part of the effort included getting the quality dashboard (https://qa.meshery.io) unstuck - it had quietly been unable to publish anything for about a day. The existing reports /meshery//mesheryctl/, and the root reports are all publishing again. 

A new report (/connections/) has been created and contains test results for the ~80 new test cases that focused on Connection Lifecycle with emphasis on Kubernetes connections. See the new report here - https://qa.meshery.io/connections/

On a related note, Yi Nuo has opened a handful of issues calling for full coverage of the “installation” test group - https://github.com/meshery/meshery/issues

Best,
Marcus

marcus ringblom

unread,
Aug 3, 2026, 1:56:00 AM (yesterday) Aug 3
to Meshery Developers
I forget to mention that each of the test case results in the qa.meshery.io dashboard are now traceable back to the test case definition in the test plan spreadsheet. 

Notice the TC-XXXX (test case-#####) hyperlink in the screenshot below.

Best,
Marcus

Screenshot 2026-08-03 at 12.53.38 AM.png

--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/64B30462-90DF-45D6-8259-3256EF03E3F2%40gmail.com.

Yi Nuo

unread,
Aug 3, 2026, 1:56:42 PM (yesterday) Aug 3
to marcus ringblom, Meshery Developers
This sort of traceability is very helpful, I think. The original test case descriptions in the test plan spreadsheet are convenient to have while reviewing test failures.

Yi

Lee Calcote

unread,
Aug 3, 2026, 2:01:00 PM (yesterday) Aug 3
to Meshery Developers, yinu...@gmail.com, Meshery Developers, marcus....@gmail.com, ian.r....@gmail.com, Matthieu EVRIN
Ian, Matthieu, I'm curious for your thoughts, though, given that tests that both of you have written are affected by this. I'm also not sure how the custom, sub-report for a specific group of test cases like Connection Lifecycle works out over the long term.

Currently, the Meshery Test Plan spreadsheet defines 9 test groups. Allure doesn't seem to have a way to present these "sub-reports" any other way than as a top-level dashboard.

- Lee

On Monday, August 3, 2026 at 12:56:42 PM UTC-5 yinu...@gmail.com wrote:
This sort of traceability is very helpful, I think. The original test case descriptions in the test plan spreadsheet are convenient to have while reviewing test failures.

Yi

On Mon, Aug 3, 2026 at 12:56 AM marcus ringblom <marcus....@gmail.com> wrote:
I forget to mention that each of the test case results in the qa.meshery.io dashboard are now traceable back to the test case definition in the test plan spreadsheet. 

Notice the TC-XXXX (test case-#####) hyperlink in the screenshot below.

Best,
Marcus

Screenshot 2026-08-03 at 12.53.38 AM.png
On Aug 3, 2026, at 12:51 AM, marcus ringblom <marcus....@gmail.com> wrote:

Hi All,

A few of us have spent time updating the Meshery Test Plan spreadsheet with about 80 new test cases under a new test group, “Connection Lifecycle”. 

Part of the effort included getting the quality dashboard (https://qa.meshery.io) unstuck - it had quietly been unable to publish anything for about a day. The existing reports /meshery//mesheryctl/, and the root reports are all publishing again. 

A new report (/connections/) has been created and contains test results for the ~80 new test cases that focused on Connection Lifecycle with emphasis on Kubernetes connections. See the new report here - https://qa.meshery.io/connections/

On a related note, Yi Nuo has opened a handful of issues calling for full coverage of the “installation” test group - https://github.com/meshery/meshery/issues

Best,
Marcus

--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+unsubscribe@meshery.io.

--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+unsubscribe@meshery.io.
Reply all
Reply to author
Forward
0 new messages