Skip to content

[mesheryctl] Add a dedicated BATS end-to-end quality report #86

Description

@Zayden369

Current Behavior

The Mesheryctl quality report combines Bash/BATS end-to-end test results with Go unit test results. There is no dedicated report for inspecting only BATS results.

Desired Behavior

Provide a separate “Mesheryctl: BATS End-to-End Tests” report while retaining the existing combined Mesheryctl report.

Implementation

Add an Allure report filtered by project=mesheryctl and framework=bats, using the existing result collection and publishing workflow. Document the report in the README.

Acceptance Tests

  • The dedicated report includes mesheryctl BATS results and excludes Go unit results.
  • The existing combined Mesheryctl report remains available.
  • Report generation succeeds.

Related Pull Request

#85

Activity

  1. MU5A commented on Sep 8, 2026

    @MU5A

    Hi @abhishek Kumar Gupta, nice fix. Lee also pointed me at this same gap in the same thread and I went looking at the meshery/meshery side of it, meshery/meshery#21845 (starting fix meshery/meshery#21846).

    Turns out the two issues are complementary, not overlapping: this one gives BATS results their own dedicated report tile, separate from the Go unit tests. The one I found is that only 45 of 185 mesheryctl BATS tests (24%) actually carry the componentUnderTest/testGroup traceability tags bats-to-allure.js supports, so even once this report is split out, most of it would still show as one flat, untagged list. Your fix and the tagging work are both needed for a genuinely useful dedicated report. Cross-linked both sides so nobody duplicates effort.

  2. Zayden369 commented on Sep 8, 2026

    @Zayden369
    ContributorAuthor

    Hi @abhishek Kumar Gupta, nice fix. Lee also pointed me at this same gap in the same thread and I went looking at the meshery/meshery side of it, meshery/meshery#21845 (starting fix meshery/meshery#21846).

    Turns out the two issues are complementary, not overlapping: this one gives BATS results their own dedicated report tile, separate from the Go unit tests. The one I found is that only 45 of 185 mesheryctl BATS tests (24%) actually carry the componentUnderTest/testGroup traceability tags bats-to-allure.js supports, so even once this report is split out, most of it would still show as one flat, untagged list. Your fix and the tagging work are both needed for a genuinely useful dedicated report. Cross-linked both sides so nobody duplicates effort.

    Thanks, @Musa Bashir! That complements the dedicated report well—separating the BATS results makes them easier to find, and the tags will make them easier to navigate. Appreciate you cross-linking the issues and PRs to keep the work coordinated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions