_Event-Sourcing Example App_
Join me in 1 hour (18:00 UTC) as I continue work on JitterTix, an example app demonstrating how to do #EventSourcing in #Java (and #SpringBoot) without ES libraries, but with #TDD.
Source code is at https://github.com/jitterted/jitterticket-event-sourced
We have a prototype of the API documentation online: https://api.xunit.net/
We're not sure if it will live on a separate URL forever, but until the main site is rebuilt with DocFX, this is how it has to be for now.
Feedback welcome!
Claude Code and the Art of Test-Driven Development
#AI #AICodeGeneration #AICodingAssistants #Anthropic #Claude #TDD
https://thenewstack.io/claude-code-and-the-art-of-test-driven-development/
We just shipped core framework v3 2.0.1 and source analyzers 1.21.0.
Check the release notes for new features and bugs fixed.
https://xunit.net/releases/v3/2.0.1
https://xunit.net/releases/analyzers/1.21.0
Sometimes it's very difficult to wrap a test around some nasty legacy code when you're fixing a bug.
My rule of thumb for whether my nasty test is "good enough" is:
Without the bug-fix, the test fails WITH A USEFUL FAILURE MESSAGE, and with the fix it passes.
_JitterTix Concert Ticketing System_
On my #Java live coding stream this week I've been working on a simple concert event ticketing system that is based on #EventSourcing. I have several reasons I've been doing this (putting my #TDD Game on hold).
TDD 
+ GenAI 
= Dream Team?
In her latest article, Karakun expert Dr. Iryna Dohndorf explores how combining Test-Driven Development with Generative AI can boost code quality and accelerate delivery. 
Read it on the #Karakun #DeveloperHub: 
https://dev.karakun.com/2025/04/02/tdd-genai.html
What do you think – can GenAI enhance your TDD flow? 
User-Interfaces im #Web mit #TDD entwickeln? Das geht nicht! Doch, sage ich. Und wie? Das zeige ich dir gemeinsam mit meinem Kollegen Christoph Muth bei unserem Talk „Erst der Test, dann die Pixel. Wie TDD auch im UI funktioniert“. Schau gerne vorbei!
https://www.meetup.com/tech-talk-stuttgart/events/306769835/
Why I like #TDD? Because I don't end up writing an overcoupled interface that pretends to be something it isn't for the sake of compatibility no one asked for because I had "an idea™".
Solve a problem in front of you, nothing more, nothing less. Do it until you run out of problems. Look back in between problems. Don't downplay problems.
The only one you're gonna outsmart with a clever code is you yourself.
PS: I spin up HTTPS servers to test API clients, by the way.
Netskope is hiring Distinguished Engineer, Client Cloud Backend
#cplusplus #golang #python #node #rest #cicd #json #kubernetes #tdd
Taipei, Taiwan
Full-time
Netskope
Job details https://jobsfordevelopers.com/jobs/distinguished-engineer-client-cloud-backend-at-netskope-com-jan-9-2025-a645ed?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
Hey Mastodon, question for my #sysadmin and #DevOps types. Has anyone used #Pester and #PSScriptAnalyzer to set up unit testing for test driven development, particularly on (relatively) simple #PowerShell scripts like you might use for application detection, installation, and uninstallation from a system like #SCCM #Intune or #ManageEngine ?
Apologies for the buzzword bingo, but I’m trying to reach folks who may be following the hashtags, but not necessarily have a connection otherwise.
"A high-risk decision is a gambling decision between a direct cost to mitigate a risk, and the potential indirect cost of ignoring the risk. One of the most common high-risk decisions in software development is skipping unit tests in an attempt to save time." - Janelle Arty Starr
I despise `it.each(testCases)` ….
Feel it’s like debugging a pile of mud…
#Java Live Coding Stream
Join me live as I continue work on the event-sourcing aspect of JitterTed's TDD Game online.
Java, #EventSourcing, #TDD, #Refactoring, mistakes, rants, and more: https://jitterted.stream
#Java Live Coding Stream
In an hour (6pm UTC) I'll be continuing work on the event-sourcing aspect of JitterTed's TDD Game online (https://tdd.cards).
Join me on Twitch for Java, #EventSourcing, #TDD, #Refactoring, mistakes, rants, and more: https://jitterted.stream
It seems like unit testing in Rust is difficult. I am looking into mockall and other mocking libraries, and I'm kind of turned off by all the macros I have to add to my code (and sometimes it even impacts the production code!) instead of being able to keep all test-related stuff in test modules. Also I don't want to use traits for everything—I'd rather not `dyn Trait` everywhere if I don't have to.
How do you effectively unit test in Rust when you have object dependencies?
