mirror of https://github.com/MingweiSamuel/Riven
0be6a3b34c
https://github.com/RiotGames/developer-relations/issues/1005 |
||
|---|---|---|
| .. | ||
| README.md | ||
| tests_americas.rs | ||
| tests_asia_jp.rs | ||
| tests_europe.rs | ||
| tests_euw.rs | ||
| tests_euw_tft.rs | ||
| tests_jp1_tft.rs | ||
| tests_kr.rs.ignored | ||
| tests_la1.rs | ||
| tests_me1.rs | ||
| tests_na.rs | ||
| tests_ph2.rs | ||
| tests_rso.rs | ||
| tests_sea.rs | ||
| tests_sg2.rs | ||
| tests_th2.rs | ||
| tests_tr_europe.rs | ||
| tests_val_latam.rs | ||
| tests_val_match_latam_na_br.rs | ||
| tests_vn2.rs | ||
| testutils.rs | ||
README.md
Tests are divided up by region. This is because tests cannot share state, and therefore
cannot share the rate limiting done within a RiotApi instance. However, rate limiting
is separate for each region, so it is safe to send requests to different regions from
different instances.
The tests within an individual file do share their RiotApi instance thanks to custom
test runners and some macros I hacked together which are located in async_tests.rs.
They are set up in a way to look like normal test output for fun and probably to
confuse people.