test/

README

Tests

Benchmark

[!WARNING] Benchmarks are currently not automated, take the results in the code comments with a grain of salt.

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

• parallel: Variety of benchmarks to test parallelism. Used more as tests than benchmarks.
• cache: Cache benchmarks for both BigCache and Redis.
• data: Benchmarks that use data from the live Riot Games API, located in the data folder.
• internal: Focused mainly on Request and Execute/ExecuteRaw and internal client functions.

Benchmarks should be using a configuration close to the one used in production. HTTPClient timeout is disabled as I believe the context should be used instead (the request is even created with http.NewRequestWithContext(ctx, ...)).

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

Integration

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

The objective of these tests is to test some methods from different games against the live Riot Games API, making sure the different HTTP methods are working as intended. Ideally, these tests should only contain methods allowed by a development key and should be only a handful of tests to avoid getting rate limited.

Run tests using:

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

or if using PowerShell:

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