Do you know your way around the #JUnit4 API? I'd love to add support for it in Greencently, my tiny #JUnit extension. How you can help: https://github.com/schmonz/junit-greencently/issues/29

#PairProgramming (if you'd like to) #TDD #JUnit5 #Kotlin #Java
implement JUnit 4 support · Issue #29 · schmonz/junit-greencently

Necessary ingredients: We need to be notified of (a) each test result and (b) the runner terminating, in a JUnit4Listener We need to discover and enumerate all tests in a given project the same way...

GitHub
Likewise for #TestNG -- if you know its API, let's support it in Greencently.

What's Greencently, you very reasonably want to know? https://github.com/schmonz/junit-greencently
GitHub - schmonz/junit-greencently: All tests green, recently? Commit quickly and stay in flow.

All tests green, recently? Commit quickly and stay in flow. - schmonz/junit-greencently

GitHub
When making an enhancement to the experience of running automated tests, a cool thing to have for it would be automated tests.

A start: https://github.com/schmonz/junit-greencently/commit/99bd02f4757923faa1fcc12e103a9e967fabdd19
Replace TESTING.md with test.sh. · schmonz/junit-greencently@99bd02f

All tests green, recently? Commit quickly and stay in flow. - Replace TESTING.md with test.sh. · schmonz/junit-greencently@99bd02f

GitHub
Struggling with JUnit 4 integration led me to an insight: for my purposes, test frameworks are the wrong extension point.

https://github.com/schmonz/junit-greencently/issues/4#issuecomment-2810303244
simplify Gradle config · Issue #4 · schmonz/junit-greencently

Users currently have to override Gradle's default parallelization... tasks.withType<Test> { maxParallelForks = 1 } ...because we haven't yet handled combining results from multiple Test Executors.

GitHub