Automated testing using command api
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there any interest in using RA’s stdin commands to set up automated testing for stuff like save states, screenshots, and now replays? Where would that go in the CI pipeline, and is there some cross platform tool we should use to run RA and compare results against expected outputs?
This wouldn’t give a way to test menu related stuff, but it would allow for testing runloop features around commands and stuff as well as CLI arguments. Does such a feature or framework exist and I’m just missing it?
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 mapping RetroArch's stdin command handling, save-state, screenshot, replay, and CLI argument paths, then review the existing CI setup for cross-platform execution. Define a concrete test scope and expected-output comparison approach before identifying the files and commands to change; done means reproducible automated coverage running across supported platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- ci-cd, cli, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100