Closed gaby closed 4 months ago
A secondary benefit of this is that it forces you to handle goroutines in a more deterministic way (eg using channels). I've seen people incorrectly assume that their goroutines are finishing by the time the test ends when in reality the test is just exiting before the assertion is run.
@nickajacks1 Yeah, definitely. I'm trying to fix the failing Client test using a channel. The proxy test failing was caused because it was using the default Timeout value for app.Test()
.
Related to https://github.com/gofiber/fiber/issues/2871
Bug Description
The latest
testify
release added a notice against usingrequire
inside a goroutine. This is something covered bytestify-lint
through thego-require
rule which is enabled by default. This rule was disabled during golangci-lint upgrade in https://github.com/gofiber/fiber/pull/2842The following tests are failing:
Partly fixed by https://github.com/gofiber/fiber/pull/2874 Testify Notice: https://github.com/stretchr/testify/pull/1392
How to Reproduce
N/A
Expected Behavior
N/A
Fiber Version
v3.0.0
Code Snippet (optional)
No response
Checklist: