You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The official docs recommend testing by setting up a real router, which makes perfect sense.
However, this by default outputs the debug mode warning for every test. And this adds a load of clutter to the output.
I've just written a simple module (to support RFC-7807 problem responses) and have two tests for it. This has several lines of output per test just because of being in debug mode.
It might be that the answer is a new gin.NewTest() method or similar that is used only for testing and that doesn't have this extra noise.
Description
The official docs recommend testing by setting up a real router, which makes perfect sense.
However, this by default outputs the debug mode warning for every test. And this adds a load of clutter to the output.
I've just written a simple module (to support RFC-7807 problem responses) and have two tests for it. This has several lines of output per test just because of being in debug mode.
It might be that the answer is a new
gin.NewTest()
method or similar that is used only for testing and that doesn't have this extra noise.How to reproduce
Expectations
The test output should be clean of any unnecessary noise.
Actual result
Environment
The text was updated successfully, but these errors were encountered: