Skip to content

test(action): restore malformed fixture and widen test-action.yml paths filter#713

Merged
rvben merged 2 commits into
rvben:mainfrom
soy-chrislo:fix/restore-malformed-fixture
Jul 12, 2026
Merged

test(action): restore malformed fixture and widen test-action.yml paths filter#713
rvben merged 2 commits into
rvben:mainfrom
soy-chrislo:fix/restore-malformed-fixture

Conversation

@soy-chrislo

Copy link
Copy Markdown
Contributor

Follow-up from the discussion on #712.

__tests__/fixtures/malformed/bad.md stopped being malformed as a side effect of 497ab92 back in April, an unrelated commit whose message says "bad.md fixture corrected to valid markdown", but that file exists specifically to be malformed for these tests. This restores it.

Nothing caught the breakage for months because test-action.yml only triggered on changes to action.yml/scripts/rumdl-action.sh. Added __tests__/fixtures/** and the workflow file itself to the paths filters so this class of breakage triggers CI going forward.

What's tested:

  • Opened a disposable PR against my own fork's main to confirm the widened paths filter actually fires on pull_request (it does)
  • All 13 Test Action jobs pass with both changes combined, including the 4 that were failing on unmodified main (test-args, test-expected-failure, test-combined-informational-with-output, test-output-file-with-violations)

soy-chrislo added 2 commits July 11, 2026 12:29
__tests__/fixtures/malformed/bad.md is used by test-action.yml to
verify the Action correctly fails/reports on malformed markdown.
497ab92 (test: add coverage for fmt command, rule aliases, and
JSONC import) added a space after "##" as an incidental side effect
of unrelated CLI test coverage work, turning this fixture into valid
markdown.

The breakage stayed invisible because test-action.yml only triggers
on changes to action.yml/scripts/rumdl-action.sh, and no PR has
touched those paths since (last green run: 2026-02-14, before
497ab92). Any future PR that does touch those paths would otherwise
surface 4 unrelated red jobs (test-args, test-expected-failure,
test-combined-informational-with-output,
test-output-file-with-violations).

Verified against a real rumdl binary: restoring the original 2-line
content yields MD018 + 2x MD022 (exit 1), and still exits 1 with the
remaining MD022s when --extend-disable MD018 is applied, matching
what all 4 affected jobs assert.
test-action.yml only triggered on changes to action.yml/scripts/rumdl-action.sh,
so a change that silently broke __tests__/fixtures/malformed/bad.md sat
undetected since April. Add __tests__/fixtures/** and the workflow file
itself to the paths filters so this class of breakage triggers CI.

@rvben rvben left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified end to end: the restored fixture trips MD018, MD041, and MD047, and still fails with MD018 disabled, which is what test-args needs. The upstream Test Action run on this PR is all green, and the fact that it triggered at all confirms the widened paths filter fires. The original pre-April fixture had a # Bad markdown title line, so this isn't byte-identical, but it's functionally equivalent for every job that uses it. Merging this first so #712 can go green.

@rvben rvben merged commit db2e0ff into rvben:main Jul 12, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants