schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
> Test-driven development (TDD) is a way of writing code that involves writing an automated unit-level test case that fails, then writing just enough code to make the test pass
(Wikipedia)
So, #TDD fans, how do you write your first test(s)? Like, how do you deal with the fact that none of the implementation you will be writing has any names yet? Do you violate this principle some and stub out implementation objects to give them names? Do you write tests that "fail" due to missing names? In a statically-typed language, how do you accomplish the later -- consider failure to compile a "test failure"?
I'm generally a fan of TDD, but I never _actually_ start from the tests. They are always something that comes later but, potentially, become a driver in the future.
AceUnit v3.0.0 is officially released!
Enjoy a new world of unit testing C with automatic test discovery!
Je suis un développeur logiciel expérimenté (20+ :) indépendant, mentor et coach, je serai disponible en février.
Si vous cherchez un coup de main pour dompter une base de code sauvage, préparer une grosse évolution ou plus généralement développer un logiciel maintenable, c'est le bon moment :)
J'interviens principalement de deux façons:
* intégré à l'équipe, je fais le taf avec vous en pair programming
* et/ou en accompagnement, je vous guide dans vos réflexions et l'implémentation (qq heures/semaine)
* tous langages/technos/environnements
* remote only ou Ambert
* déplacement ponctuel ok
* freelance
#PairProgramming (if you'd like to) #TDD #JUnit5 #Kotlin #Java
_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
_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).