Search
1000 results for “junit”
-
Stop debugging broken YAML deployments at 2am. Wladi Mitzel shows how Java teams can define, test & deploy cloud infrastructure with real #Java code instead of YAML chaos — with #JUnit, refactoring, #CI/CD & type safety: https://javapro.io/2026/05/12/stop-writing-yaml-how-to-define-test-and-deploy-your-cloud-in-pure-java/
-
Read about how "#Uber pulled off one of the largest #JUnit migrations ever, transforming over 1.25 million lines of test code in just a few months." 🚀
-
If you deleted all assertions, would your coverage drop? Probably not by much, and that’s the problem. Julius Mischok explains why #PIT mutation testing is the missing layer on top of JaCoCo.
Test your tests with PIT: https://javapro.io/2026/01/21/test-your-tests-mutation-testing-in-java-with-pit/
-
JUnit gehört in Java-Projekten zu den Werkzeugen, die du früher oder später sowieso brauchst. Nicht, weil Tests gut klingen oder weil es in Tutorials oft so gemacht wird, sondern weil du mit Tests prüfen kannst, ob dein Code das tut, was du erwartest. Genau da liegt der eigentliche Wert. Ein Tes
https://magicmarcy.de/junit-in-java-was-du-wirklich-testen-solltest
#JUnit #Java #Test #Testing #Coding #Programming #Unit-Test #Verhalten #Werkzeug #Tool
-
JUnit gehört in Java-Projekten zu den Werkzeugen, die du früher oder später sowieso brauchst. Nicht, weil Tests gut klingen oder weil es in Tutorials oft so gemacht wird, sondern weil du mit Tests prüfen kannst, ob dein Code das tut, was du erwartest. Genau da liegt der eigentliche Wert. Ein Tes
https://magicmarcy.de/junit-in-java-was-du-wirklich-testen-solltest
#JUnit #Java #Test #Testing #Coding #Programming #Unit-Test #Verhalten #Werkzeug #Tool
-
JUnit gehört in Java-Projekten zu den Werkzeugen, die du früher oder später sowieso brauchst. Nicht, weil Tests gut klingen oder weil es in Tutorials oft so gemacht wird, sondern weil du mit Tests prüfen kannst, ob dein Code das tut, was du erwartest. Genau da liegt der eigentliche Wert. Ein Tes
https://magicmarcy.de/junit-in-java-was-du-wirklich-testen-solltest
#JUnit #Java #Test #Testing #Coding #Programming #Unit-Test #Verhalten #Werkzeug #Tool
-
#JUnit 5.14.4 is released!
🐞 Bug fixes and enhancements since 5.14.3
-
#JUnit 6.1.0-RC1 is ready for testing!
✨ Built-in extensions for default locale, time zone, and system properties
🚮 Configurable TempDir deletion strategy
🧹 Experimental memory cleanup mode -
-
JUnit 5 Extensions (часть 2): пишем умные data-провайдеры и DI-контейнер на Kotlin
" Скоро сказка сказывается, да не скоро дело делается " - говорится в народной пословице. Вот и мы решили не спешить со второй частью статьи по Junit 5 Extensions, а подойти к ней более основательно! Статья будет полезна QA-автоматизаторам, которые хотят глубже понимать работу с расширениями и выжать чуть больше из связки Kotlin + Junit5. Мы пройдем путь от простой реализации condition-выполнения тестов и источников данных для параметризованных тестов до реализации расширения Микро-DI с рекурсивной инъекцией зависимостей. Как и в прошлой статье , сделаем акцент на практической части реализации расширений для JUnit 5. В качестве языка - Kotlin. Поэтому, достаем бутерброды, наливаем пиво кофе и приступаем!
-
Un outil de test BDD que j'avais déja vu, et qui semble vraiment bien pensé. https://jbehave.org/ #junit #extension #test #bdd #opensource #framework
-
Что нового в OpenIDE 2025.3: Java 25, Spring MCP, Go, Docker и JavaScript/TypeScript
Состоялся релиз OpenIDE 2025.3 на базе IntelliJ IDEA Platform 2025.3. В релизе — поддержка Java 25, автодополнение действий IDE через двойную точку (Command Completion), Spring MCP для LLM-агентов, обновления для Go и фронтенд-стека, улучшения HTTP-клиента Connekt и доработки Docker-плагина.
https://habr.com/ru/companies/haulmont/articles/1004128/
#OpenIDE_20253 #Java_25_LTS #IntelliJ_IDEA_Platform #Command_Completion #Spring_MCP #Amplicode #Go_Language_Server #Docker #Connekt_HTTP_Client #JUnit_6
-
Что нового в OpenIDE 2025.3: Java 25, Spring MCP, Go, Docker и JavaScript/TypeScript
Состоялся релиз OpenIDE 2025.3 на базе IntelliJ IDEA Platform 2025.3. В релизе — поддержка Java 25, автодополнение действий IDE через двойную точку (Command Completion), Spring MCP для LLM-агентов, обновления для Go и фронтенд-стека, улучшения HTTP-клиента Connekt и доработки Docker-плагина.
https://habr.com/ru/companies/haulmont/articles/1004128/
#OpenIDE_20253 #Java_25_LTS #IntelliJ_IDEA_Platform #Command_Completion #Spring_MCP #Amplicode #Go_Language_Server #Docker #Connekt_HTTP_Client #JUnit_6
-
Что нового в OpenIDE 2025.3: Java 25, Spring MCP, Go, Docker и JavaScript/TypeScript
Состоялся релиз OpenIDE 2025.3 на базе IntelliJ IDEA Platform 2025.3. В релизе — поддержка Java 25, автодополнение действий IDE через двойную точку (Command Completion), Spring MCP для LLM-агентов, обновления для Go и фронтенд-стека, улучшения HTTP-клиента Connekt и доработки Docker-плагина.
https://habr.com/ru/companies/haulmont/articles/1004128/
#OpenIDE_20253 #Java_25_LTS #IntelliJ_IDEA_Platform #Command_Completion #Spring_MCP #Amplicode #Go_Language_Server #Docker #Connekt_HTTP_Client #JUnit_6
-
#JUnit 6.0.3 is released!
🐞 Bug fixes and enhancements since 6.0.2
-
#JUnit 5.14.3 is released!
🐞 Bug fixes and enhancements since 5.14.2
-
Meet the #JUnit team in Cologne, Germany, in April at @jcon!
@marcphilipp will give a talk about the road to JUnit 6 and @sormuras and @LogAteWhale will be attending as well.
Please use the following link to support JUnit (10% of the proceeds will go back to the project):
https://pretix.eu/impuls/europe2026/redeem?voucher=JUNIT -
✨️ New blog post: "STF Milestone 10: Documentation improvements"
Modernizing #JUnit's documentation by adopting #Antora and hosting on @statichost
👉️ https://marcphilipp.de/blog/2026/01/25/stf-milestone-10-documentation-improvements/
Thanks to the @sovtechfund for their support!
-
Your project has 2,000 tests—and nobody knows which are #JUnit4. Jean Donato explains how @OpenRewrite and Dependency Analyzer help you migrate safely, step by step.
Stay sane during test refactors: https://javapro.io/2025/09/10/mastering-junit-navigating-between-old-and-new-versions-for-a-smarter-test-strategy/
-
Was tun, wenn #JUnit nicht mehr reicht? Christopher Olbertz zeigt, wie #AssertJ für bessere Lesbarkeit sorgt, #ArchUnit Architekturverstöße erkennt & #Mockito Tests entkoppelt.
Jetzt Teststrategie modernisieren: https://javapro.io/de/testen-mit-java-die-vielfaeltige-welt-der-test-frameworks/
-
RE: https://mastodon.social/@APIdia/115587863622237679
To get started with #JUnit 6 you can explore its API now on #APIdia. Docs largely resemble #JavaDoc but are easier to browse and include the full dependency tree, consistently linked into the docs. Many other nice features to be found. Follow me or @APIdia to learn more.
#java #jvm @junitLatest: https://apidia.net/mvn/org.junit/junit
JUnit 5: https://apidia.net/mvn/org.junit/junit/5
JUnit 4: https://apidia.net/mvn/junit/junit -
Du willst, dass dein Team systematisch testet, & das auch richtig? Christopher Olbertz zeigt dir die passenden Tools für verschiedene Testarten:
✔️ Unit-Tests, Architektur-Checks, Mocking komplexer Abhängigkeiten
Lese: https://javapro.io/de/testen-mit-java-die-vielfaeltige-welt-der-test-frameworks/
-
API documentation of #JUnit 6 is now available on #APIdia. All artifacts of the latest release are conveniently browsable in one coherent doc profile. All dependencies are available as well and consistently linked to all occurrences in the API docs. Enjoy browsing!
https://apidia.net/mvn/org.junit/junit/6 -
JUnit 6 finally unifies the testing world.
✅ Single version for all modules
✅ Java 17 baseline
✅ Faster CSV, smarter fail-fast
✅ Seamless Quarkus supportHere’s how to modernize your test suite without breaking a thing:
https://www.the-main-thread.com/p/junit6-quarkus-modern-java-testing -
JUnit 6 broke 50 repos. I’m delighted.
If a dependency bump can shatter your stack, you don't need fewer updates. You need better tests.
I maintain 50+ OSS repos as one human. I don't babysit them. I automated everything, including updates and minor releases. Many repos haven't been touched in 6 years. AS now JUnit 6 rolled in, a chunk failed. Perfect.
Why perfect? Because failure is a signal, not a disaster. Good tests mean breakage never escapes. I've had repos fail on a Java date parser change. Beautiful. I saw it before release, fixed it, moved on. During Log4Shell and Spring4Shell I didn't panic. I just waited for the next update. That's what behaviour tests are for. And no, they are not slow. If your tests crawl, your design does too.
I trust code I write. I do not trust magic. I remove convenience glue that silently rots:
I don't need MultiValueMap when Map<List> is clearer.
I don't need StringUtils.isEmpty when a simple null or empty check is obvious.
I don't need annotations that smuggle in half a framework.Every extra library is a future liability: CVEs, Licences, Security, Data Privacy, Performance, breaking changes, mental overhead. Use them to start, then delete them to last. Fewer moving parts mean fewer ways to die.
After 6 years my micro systems still boot in micro seconds, still read clean, still behave. CI pipelines aged, sure, but the code stayed boring. Boring is freedom. Quiet, peaceful, done.
If your stack cannot auto-update without heart palpitations, the problem isn't updates. It's architecture.
Principles I ship by
Automate updates and everything else I can. Let tests be the gate, not fear.
Push behaviour tests to the edges. If it's slow, refactor until it isn't.
Prefer primitives and standard libs. Delete decorative wrappers.
Design for micro systems, not micro monoliths. Start fast, stay fast.
Fewer tools, fewer surprises, fewer nights on fire.Congratulations. The system failed safely. After fix, you may proceed to do literally anything else with your life.
#java #junit #testing #oss #automation #developerexperience #simplicity #minimalism #microservices #security #log4shell #spring4shell #cleanarchitecture
-
Legacy code still stuck with #JUnit4? Jean Donato shows how hybrid setups silently rot your test base—and what you must do to regain control.
From dependency analysis to rewrite automation: https://javapro.io/2025/09/10/mastering-junit-navigating-between-old-and-new-versions-for-a-smarter-test-strategy/#Java #JUnit5 #TDD #CleanCode #JAVAPRO @OpenRewrite @BeforeEach
-
Want to migrate to #JUnit5 but stuck with legacy test libraries? Jean Donato shows how to identify hidden JUnit 4 deps, use @BeforeEach correctly, and cleanly transition with @OpenRewrite.
Read his Step-by-step guide now: https://javapro.io/2025/09/10/mastering-junit-navigating-between-old-and-new-versions-for-a-smarter-test-strategy/
-
Viele Teams nutzen JUnit & testen trotzdem ineffizient. Christopher Olbertz erklärt, wo #JUnit an Grenzen stößt & welche Tools wie #Mockito, AssertJ oder #ArchUnit gezielt weiterhelfen.
Mehr Qualität mit weniger Aufwand: https://javapro.io/de/testen-mit-java-die-vielfaeltige-welt-der-test-frameworks/
-
Want to contribute to #JUnit6?
This issue is "up for grabs"! 😎