We currently only store selective testing results when all tests succeed. However, that’s unnecessarily restrictive.
It’s quite common for selective testing solutions from other ecosystems such as Elixir with Mix to cache successful test runs even if there are other tests in the test suite that fail.
To get the metadata for which tests failed or not, we will most likely have to parse the .xcresult bundle generated by xcodebuild.
1 Like
This got now merged into main
main ← cooksimo:selective-testing-cache-passing-targets
opened 01:17AM - 28 Feb 25 UTC
### Short description 📝
This PR modifies the caching step for testing to enab… le caching of passing targets, even if they were part of a test run that ultimately failed. This way repeated test runs can benefit from the cache, and only rerun the targets that failed.
See https://community.tuist.dev/t/save-successful-test-results-even-when-others-fail/396
### How to test the changes locally 🧐
- Run a test scheme/plan with multiple targets, some failing and some passing
- Some tests will be cached
- Repeating the same command should see only the failing targets tests run
### Contributor checklist ✅
- [ ] The code has been linted using run `mise run lint-fix`
- [ ] The change is tested via unit testing or acceptance testing, or both
- [ ] The title of the PR is formulated in a way that is usable as a changelog entry
- [ ] In case the PR introduces changes that affect users, the documentation has been updated
### Reviewer checklist ✅
- [ ] The code architecture and patterns are consistent with the rest of the codebase
- [ ] Reviewer has checked that, if needed, the PR includes the label `changelog:added`, `changelog:fixed`, or `changelog:changed`, and the title is usable as a changelog entry
1 Like
