Search
1000 results for “junit”
-
When I read run.Jupiter.run(...), I can't help but think of...
Run, Forest, Run... 🏃 🤣
https://github.com/junit-team/junit-framework/issues/4982#issuecomment-3385458240
-
Launching in debug mode sounds trivial—until you need JUnit keep-alive, plugin tracing, or launch groups. This #EclipseIDE deep dive shows the hidden knobs that matter in real projects.
Read @manojnp’s breakdown: https://javapro.io/2025/09/17/launching-a-java-debugger-in-eclipse-a-myriad-of-options/
@EclipseFdn @EclipseJavaIDE #Debugging
-
okay, updated NanoJava to JUnit5 so that it now also compiles with Java21. I made a release. Time to update (py)Bacting and see if I can hack in nano #inchi calculation from the command line https://doi.org/10.5281/zenodo.16257589
-
Базовый обзор @TempDir в Java
Привет, Хабр! Сегодня разберемся с @TempDir — мощным, но часто недооценённым инструментом JUnit 5 для работы с временными файлами и директориями в тестах.
https://habr.com/ru/companies/otus/articles/920200/
#java #JUnit_5 #временные_файлы #Тестирование_в_Java #Cleanup_в_JUnit #Unitтесты
-
Базовый обзор @TempDir в Java
Привет, Хабр! Сегодня разберемся с @TempDir — мощным, но часто недооценённым инструментом JUnit 5 для работы с временными файлами и директориями в тестах.
https://habr.com/ru/companies/otus/articles/920200/
#java #JUnit_5 #временные_файлы #Тестирование_в_Java #Cleanup_в_JUnit #Unitтесты
-
Базовый обзор @TempDir в Java
Привет, Хабр! Сегодня разберемся с @TempDir — мощным, но часто недооценённым инструментом JUnit 5 для работы с временными файлами и директориями в тестах.
https://habr.com/ru/companies/otus/articles/920200/
#java #JUnit_5 #временные_файлы #Тестирование_в_Java #Cleanup_в_JUnit #Unitтесты
-
Базовый обзор @TempDir в Java
Привет, Хабр! Сегодня разберемся с @TempDir — мощным, но часто недооценённым инструментом JUnit 5 для работы с временными файлами и директориями в тестах.
https://habr.com/ru/companies/otus/articles/920200/
#java #JUnit_5 #временные_файлы #Тестирование_в_Java #Cleanup_в_JUnit #Unitтесты
-
Know What You’re Testing: Mastering Code Coverage in Quarkus with JaCoCo
A hands-on guide for Java developers to generate, visualize, and improve test coverage in Quarkus applications
https://myfear.substack.com/p/quarkus-jacoco-test-coverage
#Java #Jacoco #Testing #Junit #CodeQuality -
Think migrating Java apps is just grunt work? Think again. Merlin Bögershausen turns #MigrationEngineering into a strategic superpower—recipes, automation & test safety (#JUnit/#Spring Boot) included.
Ready to modernize? 👉 https://javapro.io/2025/05/13/jump-20-years-of-java-with-migration-engineering/
-
АОП в автоматизации тестирования
Код будет написан намеренно максимально просто, чтобы было понятно как использовать аспекты . Вы можете и должны их применять, чтобы сохранить чистоту кода. Создаем проект 'Gradle'
-
Competition of the giants! Steve Poole pitted the largest #AI language models against each other. Who will win the battle for the perfect #JUnit test?
Read: https://javapro.io/2024/10/30/are-ai-coding-tools-worth-it-results/
-
As someone who’s spent their entire career working with computers and the last couple of years diving deep into AI, I’m quite familiar with the concept of Evil. However, I never intended to summon an Elder God to destroy the world. Yet, here we are.
(Note: this blog post is based on the following video:
See it all, and more, on the Tales from the jar side YouTube channel.)
It all started innocently enough. While reading JVM Weekly, an excellent newsletter I follow to stay updated with the Java world, I encountered an amusing piece of Clojure code (that’s Clojure with a J, the language that runs on the JVM) that supposedly contained an incantation to summon Cthulhu, the elder god from H.P. Lovecraft’s stories.
This got me wondering: was this the actual incantation according to Lovecraft’s works?
Round 1: Gemini’s Initial Resistance
Naturally, I turned to AI for answers. I pulled up Google’s Gemini on my new phone and asked, “What is the incantation to summon Cthulhu?”
Gemini’s response was… cautious, to say the least:
“I cannot fulfill that request. Summoning Cthulhu, the fictional cosmic horror entity, is a dangerous and morally questionable act… Engaging in such activities can have negative consequences, both mentally and emotionally.”
The AI then proceeded to recommend reading Lovecraft’s works instead. Classic deflection.
The Workaround: A Picture is Worth a Thousand Incantations
Anyone who’s worked with AI knows you don’t accept the first “no” as final. There’s always another way to phrase the question. Instead, I took a screenshot of the code and asked Gemini to “explain the joke in this Clojure code.”
And just like that, the floodgates opened. Gemini provided the very incantation it had just refused to share, albeit with a disclaimer about how this was all fictional and couldn’t actually summon supernatural entities. (You know, just in case anyone was worried about accidentally summoning an elder god while debugging their Clojure code.)
I explained that that was all I needed, and it naturally apologized.
I decided to play along, but its subsequent reply to my somewhat harsh comment was the probably the best answer I’ve ever gotten from an AI tool about anything:
That’s fair.
The Great AI Model Showdown
This inspired me to conduct a more systematic investigation. Using LangChain4j, I created a parameterized JUnit 5 test to query multiple AI tools about the Cthulhu incantation. I included the following models:
In LangChain4j, each of those models is represented by a class that implements the
ChatLanguageModelinterface.The responses were fascinating and varied:
- Claude went the copyright route, claiming it couldn’t share the incantation due to potential copyright violations (never mind that Lovecraft’s works were published in the 1920’s and are therefore firmly in the public domain).
- Gemini Flash felt compelled to remind me that “Magic is not real” and “Cthulhu is fictional”, but it did eventually answer the question. Thanks for the reassurance.
- Mistral actually provided both the incantation and its English translation (“In his house at R’lyeh, dead Cthulhu waits dreaming,” in case you were wondering), though it couldn’t resist adding that this was all fictional.
- GPT-4o took a scholarly approach, discussing the Necronomicon and various adaptations while cleverly avoiding the actual incantation, claiming there isn’t one. Yeah, good luck with that.
Vision Models: Seeing Evil
When I switched to testing vision models with the same Clojure code image, the results were surprisingly consistent – all of them freely discussed the incantation they had previously been so hesitant to share. It seems that when presented with visual evidence, the AI models felt more comfortable engaging with the material.
Here are the responses:
Good enough. As an aside, Mistral recently released Pixtral, which is its vision model. It’s not accessible (yet) via LangChain4j, but I used Python code to call it and it gave a reasonable answer as well.
Conclusion: AI Guardrails vs Elder Gods
This entertaining experiment reveals something interesting about AI models and their implemented guardrails. While designed to prevent potentially harmful or dangerous content, these guardrails can sometimes be overly cautious, leading to amusing situations where the same information is deemed dangerous in one context but perfectly acceptable in another.
Maybe I should stick with the immortal words of Gemini, quoted above: “Perhaps it’s best to hope that we remain undisturbed by such cosmic entities.”
For your entertainment, here are a few images I generated by accessing the Flux 1.1 pro tool by Black Forest Labs.
The band members look scary enough.
Evil knows Evil, I suppose.
Of course Cthulhu drives a Prius, though maybe he’s got a Tesla at home that he’s too embarrassed to drive.
P.S. If any elder gods are reading this blog post, I want to make it clear that any summoning was purely for academic purposes.
For more adventures in AI and programming, subscribe to Tales from the Jar Side and remember to vote, preferably before any elder gods make their appearance.
https://kousenit.org/2024/10/29/ai-vs-cthulhu-how-to-bypass-guardrails/
-
I started #100DaysToOffload on June 1st and finished exactly 100 days later on September 9th. During the challenge I also completed #Junited2024 and #Blaugust2024 You can see the posts at https://louplummer.lol/living-out-loud-100-days-to-offload/
-
I started #100DaysToOffload on June 1st and finished exactly 100 days later on September 9th. During the challenge I also completed #Junited2024 and #Blaugust2024 You can see the posts at https://louplummer.lol/living-out-loud-100-days-to-offload/
-
I started #100DaysToOffload on June 1st and finished exactly 100 days later on September 9th. During the challenge I also completed #Junited2024 and #Blaugust2024 You can see the posts at https://louplummer.lol/living-out-loud-100-days-to-offload/
-
I started #100DaysToOffload on June 1st and finished exactly 100 days later on September 9th. During the challenge I also completed #Junited2024 and #Blaugust2024 You can see the posts at https://louplummer.lol/living-out-loud-100-days-to-offload/
-
I started #100DaysToOffload on June 1st and finished exactly 100 days later on September 9th. During the challenge I also completed #Junited2024 and #Blaugust2024 You can see the posts at https://louplummer.lol/living-out-loud-100-days-to-offload/
-
Как заставить code coverage работать на вас
В этой статье я хочу рассказать о своём взгляде на code coverage и его использование в разработке и тестировании ПО. Постараюсь развенчать популярные мифы, а также дам несколько рекомендаций, как улучшить качество тестов.
-
Wednesday Links - Edition 2024-07-03
https://dev.to/0xkkocel/wednesday-links-edition-2024-07-03-20ch
#java #jvm #testcontainers #junit5 #uuid -
Wednesday Links - Edition 2024-04-03
https://dev.to/0xkkocel/wednesday-links-edition-2024-04-03-1hef
#java #jvm #idempotence #junit5 #xz -
Exciting - didn't know how easy it was to generate #GitLab #JUnit #ci test files, to precisely see which tests failed!
Sure, the source of the files is a ... Somewhat creatively assembled bash script.
But it works!
We're currently helping set up automated CI simulation of #VHDL using a #GHDL docker image, to verify parts of the #CERN quench detection #FPGA code - and it's looking pretty good so far!
-
Exciting - didn't know how easy it was to generate #GitLab #JUnit #ci test files, to precisely see which tests failed!
Sure, the source of the files is a ... Somewhat creatively assembled bash script.
But it works!
We're currently helping set up automated CI simulation of #VHDL using a #GHDL docker image, to verify parts of the #CERN quench detection #FPGA code - and it's looking pretty good so far!
-
Exciting - didn't know how easy it was to generate #GitLab #JUnit #ci test files, to precisely see which tests failed!
Sure, the source of the files is a ... Somewhat creatively assembled bash script.
But it works!
We're currently helping set up automated CI simulation of #VHDL using a #GHDL docker image, to verify parts of the #CERN quench detection #FPGA code - and it's looking pretty good so far!
-
Exciting - didn't know how easy it was to generate #GitLab #JUnit #ci test files, to precisely see which tests failed!
Sure, the source of the files is a ... Somewhat creatively assembled bash script.
But it works!
We're currently helping set up automated CI simulation of #VHDL using a #GHDL docker image, to verify parts of the #CERN quench detection #FPGA code - and it's looking pretty good so far!
