Msw: Flaky: "msw-api/context/delay.test.ts" integration test

[kettanaito]

Scope

• Test: https://github.com/mswjs/msw/blob/3ca8d86aa4cee221b9965938b1f1833259d4c44b/test/msw-api/context/delay.test.ts

Current behavior

• Failed job: https://app.circleci.com/pipelines/github/mswjs/msw/725/workflows/930f804b-a669-41a1-a2cd-dccf0020fcf5/jobs/996/steps

Current deviation value (150 ms) is not sufficient to cover the random response time generated by ctx.delay().

Expected behavior

Integration test for implicit response delay passes. I recommend to setup a simple Shell script that would run that test numerous times (i.e. 100) and ensure all the runs pass.

Suggested solution

• Increase the deviation amount to 200 ms.

[kettanaito]

Hey, @JacobMGEvans! This is that flaky test issue we've been discussing on Discord. Please, feel free to take a look into it, if you have some spare time. I'd be thankful.

[JacobMGEvans]

Alright thanks! I will be able to take a look. Sorry for the delay I was experiences burnout pretty bad but I am back 😄

[cowboyd]

This is that flaky test issue we've been discussing on Discord.

@kettanaito where is the discord server? I didn't find a link anywhere in the README or on the doc site. Is it public?

[JacobMGEvans]

This is that flaky test issue we've been discussing on Discord.

@kettanaito where is the discord server? I didn't find a link anywhere in the README or on the doc site. Is it public?

I got you @cowboyd https://discord.com/channels/715220730605731931/727558537919594506

[cowboyd]

Thanks @JacobMGEvans!, but I'm getting that the invite is invalid or expired. Is that channel link, not an invite link maybe?

[JacobMGEvans]

Thanks @JacobMGEvans!, but I'm getting that the invite is invalid or expired. Is that channel link, not an invite link maybe?

Give me a minute.

[JacobMGEvans]

https://kentcdodds.com/discord

@cowboyd This should work. The MSW is in one of the channels 😄

[JacobMGEvans]

So I ran the tests locally with a script about 100 times, it broke on the 150 deviations about 30% if the time pretty consistently. I tried running it on a faster machine to make sure it wasn't resources related and added Jest Workers to the pool, it was pretty much the same.
PR #316