test/

Tests

Benchmark

Keep in mind that since requests are mocked using httpmock, results (time, bytes, allocs) will be different from production, specially since you can't make 300000 requests in 1 second to the Riot Games API.

Benchmarks clients should be using a configuration close to the one used in production. Some benchmarks are mainly used for testing purposes, check comments.

Benchmarks are separated in four files: parallel, data, cache and internal.

• parallel: Variety of benchmarks to test parallelism. Used more as tests to check for race conditions.
• cache: Cache benchmarks for both BigCache and Redis.
• data: Benchmarks that use data from the live Riot Games API.
• internal: Focused on InternalClient functions.

Command to run benchmarks and generate a markdown table:

go test ./test/benchmark/ -bench=. -benchmem -v | ./test/benchmark.sh

Results

Using WSL2 on a Ryzen 7 2700.

Integration

[!NOTE] Integration tests are only meant to be run manually.

The objective of these tests is to run some methods from different games against the live Riot Games API, making sure different HTTP methods are working as intended.

Run tests using:

RIOT_GAMES_API_KEY=RGAPI... go test -tags=integration ./test/integration -v -failfast

or if using PowerShell:

$env:RIOT_GAMES_API_KEY="RGAPI..."; go test -tags=integration ./test/integration -v -failfast; Remove-Item Env:RIOT_GAMES_API_KEY