GitHub-issue test parsing + harness (3/4)#103
Open
gaurav wants to merge 2 commits into
Open
Conversation
GitHubIssueTest / GitHubIssuesTestCases pull BabelTest assertions embedded
in GitHub issue bodies (wiki {{BabelTest|...}} markers or fenced YAML
blocks), resolve each to an assertion handler from the assertions package,
and evaluate it against NodeNorm/NameRes. Add the dependencies this needs:
pygithub, pyyaml, tqdm and python-dotenv.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Dynamically generate one pytest per GitHub issue (across the repos listed in targets.ini [DEFAULT] Repositories), each running the issue's BabelTest assertions as independent subtests. Open-issue failures are reported as xfail so they don't block CI. Add a --issue option (and selected_github_issues fixture) to restrict a run to specific issues, wipe the issues cache at session start, parallelize with pytest-xdist, and add a PR workflow that runs the offline `-m unit` suite. tests/github_issues/ test_system.py covers the parsing/dispatch logic with mocked GitHub data. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jun 26, 2026
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
1 participant
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.
Stack 3 of 4 splitting #67. Base:
split/2-assertions(PR #102) — review/merge #101 then #102 first.The original goal of #67: pull BabelTest assertions out of GitHub issues and run them as tests. Two commits:
sources/github) —GitHubIssueTest/GitHubIssuesTestCasesextract assertions from issue bodies (wiki{{BabelTest|...}}markers or fenced YAML), resolve each to an assertions handler, and evaluate against NodeNorm/NameRes. Addspygithub,pyyaml,tqdm,python-dotenv.tests/github_issues) — one pytest per issue (across repos intargets.ini [DEFAULT] Repositories), each assertion a subtest; open-issue failures reported as xfail. Adds--issueto target specific issues, a-m unitPR workflow, andpytest-xdist/pytest-subtests.test_system.pycovers parsing/dispatch with mocked GitHub data.Verify
uv run pytest -m unit -q→ 36 passed, 26 deselected, no token, fully offline (mockedtest_system.py+ assertions docs test).GITHUB_TOKEN=… uv run pytest tests/github_issues --target dev, optionally--issue <org/repo#N>.🤖 Generated with Claude Code