[Add] --add-status-column flag for an aggregated, colour-coded outcome column#10
Merged
samatstariongroup merged 1 commit intoSTARIONGROUP:developmentfrom Apr 24, 2026
Conversation
samatstariongroup
approved these changes
Apr 22, 2026
|
…e column
Adds a `--add-status-column` (`-st`) flag to the spreadsheet report. When
enabled, vcdg appends a `STATUS` column with one of:
(empty) no test cases — uncovered, default state
Passed all test cases pass — green cell
Failed any test case fails — red cell
Mixed some Passed + some non-Passed non-Failed — orange
Inconclusive no Passed and no Failed (only Skipped/Inconclusive) — grey
Backwards compatible: the flag defaults to `false`, so existing CLI
invocations and downstream consumers see no schema change. The status
aggregation rule is exposed as a static helper (`ReportGenerator.DeriveStatus`)
so callers that build their own reports can reuse it.
Aggregation tests cover all five branches; the existing `Verify_..._Generate`
mock is updated to match the new four-parameter signature.
Motivation: today the TESTCASES column embeds outcome as free text
("Foo - Passed\nBar - Failed"), which makes filtering "show me what's
not green" awkward. A dedicated Status column with a colour fill is a
single-line CLI flip that turns the report into a one-glance status
dashboard.
fabiantax
force-pushed
the
feature/status-column
branch
from
a166119 to
2ff5e0d
Compare
samatstariongroup
merged commit 1a2ff89
into
STARIONGROUP:development
2 of 3 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
--add-status-column(-st) CLI flag to the spreadsheet report. When enabled, vcdg appends aSTATUScolumn with one of:PassedResult == \"Passed\"#C6EFCE)FailedResult == \"Failed\"(failures dominate)#FFC7CE)Mixed#FFEB9C)Inconclusive#D9D9D9)Why
Today the
TESTCASEScolumn embeds outcome as free text (\"Foo - Passed\\nBar - Failed\"), which makes filtering "show me what's not green" awkward. A dedicatedSTATUScolumn with a colour fill turns the report into a one-glance status dashboard.This is a strictly additive change —
--add-status-columndefaults tofalseso existing CLI invocations and downstream consumers (parsers, dashboards) see no schema change.What changed
IReportGenerator.Generate— appended optionalbool addStatusColumn = false. Source-compatible with all current callers.ReportGenerator.GenerateSpreadsheetReport— when the flag is set, appends aSTATUScolumn to theDataTable, and afterInsertTablewalks the new column to apply the per-status background fill.ReportGenerator.DeriveStatus(Requirement)— new public static helper that exposes the aggregation rule so external consumers can reuse it.GenerateCommand— registers--add-status-column/-stand forwards to the handler.DeriveStatus, plus a smoke test for the spreadsheet path with the flag enabled. The existing MoqVerify(... Generate(...))was updated to the new four-parameter signature.Validation
dotnet test— 19 passed, 0 failed (was 13 passed; +6 new).Notes