rtmx-ai / rtmx / 28752664724
83%

DEFAULT BRANCH: main
Ran
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
28752664724

push

github

web-flow 
feat(from-pytest): multi-file JUnit + JUnit-driven marker discovery (package layouts) (#130)

* fix(rtmx): align pkg/rtmx req-id pattern with the results/markers default

The public marker API's reqIDPattern lacked the optional trailing lowercase
letter that internal/results.DefaultReqIDPattern and internal/markers already
accept, so a decomposition-child id like REQ-HW-STRUCT-002c validated on the
results/scan paths but would be rejected by pkg/rtmx. Add the `[a-z]?` suffix so
the three patterns agree, and cover it in TestReqIDPattern.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* feat(from-pytest): multi-file JUnit ingestion + JUnit-driven marker discovery

Two improvements that let `rtmx from-pytest --no-run` consume a sharded CI
matrix's reports directly, retiring the bespoke pre-processing downstream
projects (the Phoenix radar RTM) carried around it.

REQ-LANG-030 — multi-file --junitxml: the flag is now repeatable and each value
is glob-expanded, so `--junitxml 'output/junit-*.xml'` ingests every per-leg
report as one result set (duplicates de-duplicated; a literal non-matching path
is preserved so a truly missing file still errors). Removes the need for a
hand-rolled junit merge.

REQ-LANG-031 — JUnit-driven marker discovery: with --no-run, markers are now
discovered from the source files referenced by the JUnit cases (from each case's
`file` attribute, or its dotted class name when absent), in addition to the given
test paths. The class-name→path resolution is hyphen-safe (dots become slashes,
hyphens preserved, a trailing ClassName is dropped), so tests under a package
layout — including non-importable hyphenated dirs like
packages/signal-processing/tests — join without the caller enumerating every
directory. A missing implicit `tests` path is tolerated when the JUnit yields
markers. This was the actual cause of downstream "hyphenated package" drops: the
scan only covered the default path, not that from-pytest can't handle hyph... (continued)
Source Files on build 28752664724
Detailed source file information is not available for this build.