• some clock uses seconds precision, and test runs faster ‣
• slices comparison that depends on order of elements https://github.com/status-im/status-go/pull/4781
• Using timeouts in tests https://github.com/status-im/status-go/pull/4800
• don’t wait for absence of something https://github.com/status-im/status-go/pull/4367
• don’t change global variables in tests. Expect test to run in parallel. https://github.com/status-im/status-go/pull/5104 https://github.com/status-im/status-go/pull/5757
• Waiting for community permissions / keys distribution https://github.com/status-im/status-go/pull/5076
• Clear MobileSignalHandler on test finish https://github.com/status-im/status-go/pull/5311 signal.SetMobileSignalHandler(nil) is required. Otherwise the test might hang, because some channel is never read.

If an extremely flaky test found and you eager to comment it out, don’t. Just use:

t.Skip("flaky test")

This is a bad approach: https://github.com/status-im/status-go/pull/4741