When sequential tests aren't
Read OriginalThe article details a bug encountered when testing a Go auth service, where using sync.Once for database initialization in tests failed sporadically in CI. This was due to Go building and testing packages in parallel by default, causing race conditions, combined with test result caching introduced in Go 1.10. The author explains the root cause and presents fixes, including disabling parallelism with `-p=1` or disabling the cache with `-count=1`.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
The Beautiful Web
Jens Oliver Meiert
•
2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes
4
Wagon’s algorithm in Python
John D. Cook
•
1 votes
5
An example conversation with Claude Code
Dumm Zeuch
•
1 votes