Thats a good question <@UNS5A38D6>. In terms of t...

# test

[dmcg]

Thats a good question @Xavier F. Gouchet.

In terms of the lifecycle there is nothing unsafe about using @BeforeEach. I’m going to stick to my guns though and say that making properties mutable in order to do this decreases our ability to reason with the tests, and as such is wrong, if not inherently so 😉 .

Perhaps more harmful than that is that even highly experienced developers don’t understand the actual JUnit lifecycle because of the misdirection of initialisation in @BeforeEach, and I have definitely seen that lead to tests that were not running as they expected.