Re: [rspec] Abridged summary of rspec@googlegroups.com - 1 update in 1 topic

[Christopher Irish]

How does this compare to something like turbo tests?  https://github.com/serpapi/turbo_tests

I've had great success with it for local test runs.  And use Github Actions for parallel runs on CI

On Mon, Apr 17, 2023 at 12:43 PM <rs...@googlegroups.com> wrote:

rs...@googlegroups.com

Google Groups

Today's topic summary
View all topics

• [ANN] rspec-abq for running rspec test suites in parallel - 1 Update

[ANN] rspec-abq for running rspec test suites in parallel

Dan Manges <d...@rwx.com>: Apr 17 09:46AM -0700 Hey everybody,   We just released a new open source library for running RSpec test suites in parallel, either locally or across multiple CI jobs, and I wanted to share it with the RSpec ...more

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to rspec+un...@googlegroups.com.

--

Chris Irish

Velocity Labs

http://velocitylabs.io

[Dan Manges]

For running tests in parallel on a single machine, turbo_tests is a great option. There are a few small benefits that ABQ has which I'll detail below.

For running tests in parallel on GitHub Actions, how are you splitting the test files across multiple jobs? Typically, most approaches I've seen pre-partition test files into separate groups. Commonly, that approach results in partitions which are imbalanced, with some jobs finishing before others. Since ABQ is queued-based, it finishes the tests as efficiently as possible. I wrote a little bit more about the difference between pre-partitioning and using a queue under "Reasons for Queue-Based Parallelization" in the announcement blog post:

https://www.rwx.com/blog/abq-1-3-generally-available-open-source-release

For the use case of running in parallel locally, one difference between turbo_tests and ABQ is that ABQ wraps the native test framework CLI. So whereas turbo_tests does not support every option that the rspec CLI supports, ABQ does. You invoke ABQ as `abq test -- {any test command goes here}`, such as `abq test -n 2 -- rspec --example 'part of test description'`

ABQ is also a universal test runner, so you can learn to use it once and then apply it across multiple testing frameworks, rather than needing a language-specific solution for each framework that you use. ABQ currently supports RSpec, Jest, Playwright, and pytest.

Dan