Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/leonid-shevtsov/split_tests

Utility to split test files into parallel CI containers
https://github.com/leonid-shevtsov/split_tests

circle-ci continuous-integration travis-ci

Last synced: about 1 month ago
JSON representation

Utility to split test files into parallel CI containers

Host: GitHub
URL: https://github.com/leonid-shevtsov/split_tests
Owner: leonid-shevtsov
Created: 2017-02-07T10:50:16.000Z (almost 8 years ago)
Default Branch: master
Last Pushed: 2024-06-27T23:34:56.000Z (6 months ago)
Last Synced: 2024-10-12T18:29:07.307Z (2 months ago)
Topics: circle-ci, continuous-integration, travis-ci
Language: Go
Size: 21.5 KB
Stars: 48
Watchers: 3
Forks: 16
Open Issues: 2
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md

Awesome Lists containing this project

README

# split_tests

Splits a test suite into groups of equal time, based on previous tests timings.

This is necessary for running the tests in parallel. As the execution time of test files might vary drastically, you will not get the best split by simply dividing them into even groups.

## Compatibility

This tool was written for Ruby and CircleCI, but it can be used with any file-based test suite on any CI.
Since then, CircleCI has introduced built-in test splitting. Also since then, the tool has been applied on
GitHub Actions, that does not provide native test splitting.

There is a [split-tests GitHub Action](https://github.com/marketplace/actions/split-tests) using this tool available on the Actions Marketplace.

It is written in Golang, released as a binary, and has no external dependencies.

## Usage

Download and extract the latest build from the releases page.

### Using the CircleCI API

Get an API key and set `CIRCLECI_API_KEY` in the project config.

```
rspec $(split_tests -circle-project github.com/leonid-shevtsov/split_tests)
```

(The tool returns the set of files for the current split, joined by spaces.)

### Using a JUnit report

```
rspec $(split_tests -junit -junit-path=report.xml -split-index=$CI_NODE_INDEX -split-total=$CI_NODE_TOTAL)
```

Or, if it's easier to pipe the report file:

```
rspec $(curl http://my.junit.url | split_tests -junit -split-index=$CI_NODE_INDEX -split-total=$CI_NODE_TOTAL)
```

### Naive split by line count

If you don't have test times, it might be reasonable for your project to assume runtime proportional to test length.

```
rspec $(split_tests -line-count)
```

### Naive split by file count

In the absence of prior test times, `split_tests` can still split files into even groups by count.

```
rspec $(split_tests)
```

## Arguments

```plain
$./split_tests -help

-circleci-branch string
Current branch for CircleCI (or set CIRCLE_BRANCH) - required to use CircleCI
-circleci-key string
CircleCI API key (or set CIRCLECI_API_KEY environment variable) - required to use CircleCI
-circleci-project string
CircleCI project name (e.g. github/leonid-shevtsov/split_tests) - required to use CircleCI
-glob 'pattern'
Glob pattern to find test files (default 'spec/**/*_spec.rb'). Make sure to single-quote the pattern to avoid shell expansion.
-exclude-glob 'pattern'
Glob pattern to exclude test files. Make sure to single-quote as well.
-help
Show this help text
-junit
Use a JUnit XML report for test times
-junit-path string
Path to a JUnit XML report (leave empty to read from stdin; use glob pattern to load multiple files)
-line-count
Use line count to estimate test times
-split-index int
This test container's index (or set CIRCLE_NODE_INDEX) (default -1)
-split-total int
Total number of containers (or set CIRCLE_NODE_TOTAL) (default -1)
```

## Compilation

This tool is written in Go and uses Go modules.

- Install Go
- Checkout the code
- `make`

---