ABQ v1.3.0

ABQ is a universal test runner for parallelizing your test suite. ABQ needs no custom configuration to integrate with your test suite, making integration as easy as installing an ABQ plugin and prepending abq test -- to your existing test command.

ABQ works locally and on all CI providers. It’s the best tool for splitting test suites into parallel jobs in CI.

Get started with ABQ at rwx.com/abq.

Highlights of ABQ include:

• Optimal parallelization of your test suite using ABQ's message queue strategy of distributing tests.
  • ABQ's distribution strategy is designed to minimize network overhead, even if the message queue is far away.
• Parallelization of a test suite across any number of machines, with abq test --worker <worker number>.
• Running multiple parallel test processes in one invocation of abq test via the -n CLI flag.
• Automated retries of tests via the --retries flag to abq test.
• Manual retries of abq test nodes, that retry only the tests they ran the first time around.
• Test result reporting how you want it - ABQ won't interfere with your test framework's configured reporters.
  • ABQ also comes with standardized test result reporters, like --reporter dot, that can be used to enhance the reporters of your underlying test framework.
  • ABQ supports several structured reporters, like JUnit XML and RWX v1 JSON, so that you can export your test results in a machine-readable format without hassle.
• Aggregation of test results from all abq test nodes via abq report.
• ABQ is distributed as a standalone binary with all dependencies statically linked. All you need to run abq test, or self-host an ABQ queue, is to download the binary for your platform.
• Seamless integration with Captain.

This version of ABQ supports ABQ native runner protocol 0.2. 1.3.0 is the first public release of ABQ.

Learn more about using ABQ at the docs.