Lucas Roesler • 2/1/2019

When sequential tests aren't

Read Original

The 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`.

0 comments
#Go Testing #Test Parallelization #Database Testing
When sequential tests aren't

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
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes