social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

489
active users

#tdd

4 posts4 participants0 posts today

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.

Coming soon to Maven Central, com.schmonz:junit-greencently:20250402171221.0.0-g7a4aa00-14225507806-1:

- Also set status when not complete or green (tx Ron)
- Setup-free .gitignore (tx Llewellyn)
- Refactorings (tx Llewellyn, Petar)
- TrunkVer (tx Raimo & Chris)

#JUnit5 #TDD

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.

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?

BLOGPOST: A pleasant diversion with #TDD

I was recently nerd-sniped (in a good way) by a blogpost from @RonJeffries so I tried my hand at the problem myself and wrote up as I went.

As a bonus, almost all of the blogpost (minus some minor typo corrections and code samples) is generated directly from the commit history!

blog.probablyfine.co.uk/2025/0

Probably FineA pleasant diversion with TDD

This is brilliant advice. In times of "vibe coding" just… turn off AI agents for a bit and slowly, meticulously practice your chops with Katas: Take small, deliberate steps and great things will happen when you re-enable your AI assistant.

youtu.be/ZW4AEKbHE28

P.S. I do use AI tools (a lot!). But I don’t "vibe code," just like I never blindly copied and pasted code from Stack Overflow without understanding it.

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.