ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #junit
Learn how JUnit Jupiter’s @TempDir annotation automatically creates and cleans up temporary directories, eliminating manual cleanup and improving test reliability.
Learn how JUnit 5's @RepeatedTest runs a test method multiple times, why it helps expose flaky behavior, and what trade‑offs to watch for.
An architecture note on JUnit parameterized tests: when the design pays off, how JUnit 4's runner differs from JUnit 5's @ParameterizedTest, and how to verify each invocation actually runs.
When writing a JUnit test that aims to confirm a memory leak has been fixed, a common approach is to hold a java.lang.ref.WeakReference to the suspect object, clear strong references, and then check that the reference has been cleared. The goal is to assert that after the test’s teardown phase (e.g., an @After or @AfterEach method) the weakly‑referenced obje
java