acceptance tests: hook up to CI
Open
Nobody has claimed this yet.
testing
- Dominant language
- Jupyter Notebook
- Stars
- 5
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 17
Description
Hook up acceptance tests to optionally run in CI
Maybe run when a certain label is attached? Or manual run from button press (can we manually trigger GH actions? don't think so but not sure)
CI tests must leave a good amount of output in a readable way - so xunit integration may be important here
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the acceptance-test command and the repository's existing CI workflow. Check the proposed label or manual trigger options, then determine how CI should present readable results and whether xUnit integration is needed. Done means acceptance tests can run optionally in CI and their results are easy to inspect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100