Clarify cache behavior with parallel test processes
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 177
- Forks
- 4
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 1
Description
Hi! Thanks for FixtureKit.
I'd like to clarify how the cache behaves with process-based parallel tests such as parallel_tests.
The docs mention that cache data is mounted per connection_pool. If multiple test processes use the same cache_path, can cache files generated by one process be reused by the other processes, or is the cache effectively scoped to each process/connection pool?
If the cache is shared across processes, would you consider mentioning this explicitly in the docs?
I think this would be helpful since teams using FixtureKit for large test suites are also likely to run tests in parallel.
Contributor guide
No contributing guide indexed for this repository
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 with the documentation's cache section and investigate cache_path and connection_pool behavior when tests run through parallel_tests. Confirm whether separate processes reuse cache files; done means the docs explicitly describe the observed process and connection-pool scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100