testmycode / testmycode/tmc-server
Run tests concurrently
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 51
- Forks
- 42
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 1
Description
The test suite is extraordinarily slow. Make it possible to run tests concurrently.
One way might be to use Vagrant to clone multiple dev VMs and have some test parallellizing solution distribute the tests to the VMs. One downside is that those with virtualized development environments (i.e. the mac hippies) may have trouble running Vagrant because that would imply nested virtualization.
Without Vagrant or similar, at least the following must be considered:
- Enabling multiple sandboxes in the test sandbox server, or some other solution.
- Having multiple test databases.
- Having multiple test temp dirs.
- Having multiple comet servers.
- Finding a way to run rspec specs in parallel.
Work estimate: 1 week.
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 the test sandbox server, test databases, temporary directories, comet servers, and RSpec execution mentioned in the issue. Determine how concurrent workers could isolate each resource and how tests would be distributed. Done means the suite runs concurrently without resource collisions and the existing tests remain reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100