Project

turbo_test

0.03
Low commit activity in last 3 years
There's a lot of open issues
No release in over a year
turbo_testioquatix/turbo_testHomepageDocumentationSource CodeBug TrackerWiki
Press the turbo button... for your tests.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
 Popularity
Downloads
37,370
Stars
102
Forks
6
Watchers
15
 Releases
Current version
0.2.0
Total releases
4
First release
2020-11-01
Latest release
2022-12-08
 Issues
Open Issues
7
Closed Issues
4
Total Issues
11
Issue Closure Rate
36%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2021-08-05
Reverse Dependencies
0

 Dependencies

Runtime

async-container
>= 0
async-io
>= 0
msgpack
>= 0
rspec
>= 0
samovar
>= 0
 Project Readme

TurboTest

Development Status

Proposal

Discourse contains two tools (highly recommend you try them out for context)

  • bin/turbo_rspec a parallel runner with non interleaving forking model. (leverages some of parallel_test … rake parallel:create / migrate to prep the dbs.
  • bin/rake autospec an automatic spec runner, which focuses on failed specs, like guard except that unlike guard it is interruptible.

Enter turbo_test (name TBD, suggestions welcome).

turbo_test will be a slot in replacement for the 2 tools Discourse use in a dedicated gem.

turbo_test is to first be fully functional with rspec runners but longer term should also work with minitest.

Features of the turbo_test gem:

  • MIT license, standard Rails code of conduct
  • Pull based model for forked test runners. Master process manages a queue of tests, forked processes pull from the queue. Transport long term is agnostic though I would recommend initial implementation uses pipes.
  • Pull model ensures that all the workers are running tests at all times. The parallel_test model of splitting up the tests upfront means that workers are often idle for long periods of time.
  • Rake tasks for administration of partitioned test environments turbo_test:create / migrate / drop
  • Non interleaved results (like bin/turbo_rspec)
  • While turbo_rspec is running, if you hit a specific key you can see right away information about the current tests that failed without halting the test process.
  • Documentation about how to handle custom sharding (memcached / redis) and so on.
  • Minimal changes required to Rails projects that decide to use this.
  • A key goal is deprecation of bin/turbo_rspec in Discourse.
  • Minimal dependencies (no explicit rspec, minitest, redis, pg dependencies)
  • Stretch goal, once this is all done … extract bin/rake autospec into this gem as well. (I will do a mini specification if we get there)
  • Extra long term stretch goal, pull these concepts back into Rails proper.

Why not guard?

Guard at the moment does not support interruptible tests, this is a must have feature for turbo_test.

Why not parallel_test?

It does not support a pull model so it would be close to a ground up re-write.