f1dfd76b98
Fixes one of the 'erratic' tests It used a timer to sleep. But time also goes on when doing other things, so depending on hardware, the timings could be off. I slightly changed the tests so we still test what we functionally want. Instead of waiting until the cache expires I now have a function to expire the test and use that. That means we're not testing any more if the cache really expires after a certain amount of time, but that's the responsability of the dependency imo, so shouldn't be a problem. I also changed `Pleroma.Web.Endpoint, :http, :ip` in the tests to `127.0.0.1` Currently it was set to 8.8.8.8, but I see no reason for that and, while I assume that no calls are made to it, it may come over as weird or suspicious to people. Co-authored-by: Ilja <ilja@ilja.space> Reviewed-on: https://akkoma.dev/AkkomaGang/akkoma/pulls/233 Co-authored-by: ilja <akkoma.dev@ilja.space> Co-committed-by: ilja <akkoma.dev@ilja.space> |
||
---|---|---|
.. | ||
activity_pub | ||
admin_api | ||
akkoma_api | ||
api_spec | ||
auth | ||
common_api | ||
feed | ||
mastodon_api | ||
media_proxy | ||
metadata | ||
o_auth | ||
o_status | ||
pleroma_api | ||
plugs | ||
preload/providers | ||
push | ||
rich_media | ||
static_fe | ||
twitter_api | ||
views | ||
web_finger | ||
common_api_test.exs | ||
fallback_test.exs | ||
federator_test.exs | ||
gettext_test.exs | ||
manifest_controller_test.exs | ||
masto_fe_controller_test.exs | ||
media_proxy_test.exs | ||
mongoose_im_controller_test.exs | ||
node_info_test.exs | ||
rel_me_test.exs | ||
streamer_test.exs | ||
uploader_controller_test.exs | ||
web_finger_test.exs |