Beware mutable shared static state
Static mutable fields persist across tests and requests, creating order-dependent bugs and races. Keep state local or encapsulate it, and synchronize or use concurrency-safe structures when sharing is required.
Good to see "Beware mutable shared static state" written down. Handy reference for anyone working with java / concurrency.
Clear note on java / concurrency. "Beware mutable shared static state" is the kind of detail that is easy to overlook.
Appreciate the write-up on "Beware mutable shared static state". Useful for anyone using java / concurrency.
Surefire reuses forked JVMs by default, so static state can leak between test classes in the same run. Seen another edge case with this? Add it below.
Clear note on java / concurrency. "Beware mutable shared static state" is the kind of detail that is easy to overlook.
Specific and to the point: "Beware mutable shared static state". Worth a look if you touch java / concurrency.
Clear note on java / concurrency. "Beware mutable shared static state" is the kind of detail that is easy to overlook.
Appreciate the write-up on "Beware mutable shared static state". Useful for anyone using java / concurrency.
Good to see "Beware mutable shared static state" written down. Handy reference for anyone working with java / concurrency.