tests

Integration Tests

Running the tests

Start a redis server

To start a redis server without persistence, you can run:

echo -e 'save ""\nappendonly no' | redis-server -

The test script

From the tests directory, to run the integration tests with all languages, use:

./run-test.sh -t go_jobs,python_jobs,rust_jobs,node_jobs,dotnet_jobs

To do the same, but wit the DotNet implementation of the cleaner, use:

./run-test.sh -t go_jobs,python_jobs,rust_jobs,node_jobs,dotnet_jobs -c ./dotnet-cleaner/run.sh

To do the same, but wit the Go implementation of the cleaner, use:

./run-test.sh -t go_jobs,python_jobs,rust_jobs,node_jobs,dotnet_jobs -c ./go-cleaner/run.sh

For a summary of other options, run:

./run-test.sh --help

Options

-- tests

You can use the --tests command to test specific implementations.

For example:

./run-test.sh --tests "go_jobs,python_jobs"

--host

This can be used to set a specific redis server, the default is localhost:6379.

For example:

./run-test.sh --tests "go_jobs,python_jobs" --host example.server.net:port

--cleaner

This sets a custom binary to be used to clean the work queues, see the docs in job-spawner-and-cleaner.py.

Unit tests also exist

Each client implementation contains some unit tests. These are located within the implementations directory.

This directory contains the source for example workers, in each language, and a script to spawn jobs and check the workers behave as expected.