home.social

#tdd — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #tdd, aggregated by home.social.

  1. 🐍 Want to start learning Python?

    Join the workshop “Primi passi in Python con il TDD” at #PyConIT26 and explore Python fundamentals while writing your first tests.

    ⚠️ Limited seats.

    👇 Details and registration:
    🔗 eventbrite.it/e/primi-passi-in

    #PyConIT #PyConItalia #Python #TDD

  2. 🐍 Want to start learning Python?

    Join the workshop “Primi passi in Python con il TDD” at #PyConIT26 and explore Python fundamentals while writing your first tests.

    ⚠️ Limited seats.

    👇 Details and registration:
    🔗 eventbrite.it/e/primi-passi-in

    #PyConIT #PyConItalia #Python #TDD

  3. 🐍 Want to start learning Python?

    Join the workshop “Primi passi in Python con il TDD” at #PyConIT26 and explore Python fundamentals while writing your first tests.

    ⚠️ Limited seats.

    👇 Details and registration:
    🔗 eventbrite.it/e/primi-passi-in

    #PyConIT #PyConItalia #Python #TDD

  4. 🐍 Want to start learning Python?

    Join the workshop “Primi passi in Python con il TDD” at #PyConIT26 and explore Python fundamentals while writing your first tests.

    ⚠️ Limited seats.

    👇 Details and registration:
    🔗 eventbrite.it/e/primi-passi-in

    #PyConIT #PyConItalia #Python #TDD

  5. 🐍 Want to start learning Python?

    Join the workshop “Primi passi in Python con il TDD” at #PyConIT26 and explore Python fundamentals while writing your first tests.

    ⚠️ Limited seats.

    👇 Details and registration:
    🔗 eventbrite.it/e/primi-passi-in

    #PyConIT #PyConItalia #Python #TDD

  6. Uso #ExtremeProgramming da quando facevo #debugging all'università, oltre 20 anni fa.

    Una cosa non cambia: scrivere codice è facile, definirne tutto il comportamento no.

    🎤 A #PyConIT 2026 porterò un #workshop su #Python 🐍 e #TDD:
    dalle variabili al primo test, per chiarire cosa il software debba fare prima di implementarlo.

    2026.pycon.it/it/event/primi-p

    #TalksAndWorkshops #python #pytest #BestPractices

  7. Uso #ExtremeProgramming da quando facevo #debugging all'università, oltre 20 anni fa.

    Una cosa non cambia: scrivere codice è facile, definirne tutto il comportamento no.

    🎤 A #PyConIT 2026 porterò un #workshop su #Python 🐍 e #TDD:
    dalle variabili al primo test, per chiarire cosa il software debba fare prima di implementarlo.

    2026.pycon.it/it/event/primi-p

    #TalksAndWorkshops #python #pytest #BestPractices

  8. It took me a while (bc I'm lazy), but I finally integrated my test framework Icaro with my build system Dedalo (as it was intended to be from the beginning).

    It's still a bit awkward to set up, but `ddl test` successfully compiles and runs the tests placed in `tests/tests.cpp`.

    I'm sure there'll be a lot of bugs, but it's growing nicely.

    gitlab.com/ludusestars/dedalo

    #cpp #testing #tdd #handmade

  9. It took me a while (bc I'm lazy), but I finally integrated my test framework Icaro with my build system Dedalo (as it was intended to be from the beginning).

    It's still a bit awkward to set up, but `ddl test` successfully compiles and runs the tests placed in `tests/tests.cpp`.

    I'm sure there'll be a lot of bugs, but it's growing nicely.

    gitlab.com/ludusestars/dedalo

    #cpp #testing #tdd #handmade

  10. It took me a while (bc I'm lazy), but I finally integrated my test framework Icaro with my build system Dedalo (as it was intended to be from the beginning).

    It's still a bit awkward to set up, but `ddl test` successfully compiles and runs the tests placed in `tests/tests.cpp`.

    I'm sure there'll be a lot of bugs, but it's growing nicely.

    gitlab.com/ludusestars/dedalo

    #cpp #testing #tdd #handmade

  11. Dojo de programmation (vendredi) @ Shodo

    15 mai 2026, 19:00:00 UTC+02:00 - GMT+02:00 - Shodo, 75011, Paris, France

    mobilizon.fr/events/dd334825-5

  12. Dojo de programmation (vendredi) @ Shodo

    15 mai 2026, 19:00:00 UTC+02:00 - GMT+02:00 - Shodo, 75011, Paris, France

    mobilizon.fr/events/dd334825-5

  13. Dojo de programmation (vendredi) @ Shodo

    15 mai 2026, 19:00:00 UTC+02:00 - GMT+02:00 - Shodo, 75011, Paris, France

    mobilizon.fr/events/dd334825-5

  14. Dojo de programmation (vendredi) @ Shodo

    15 mai 2026, 19:00:00 UTC+02:00 - GMT+02:00 - Shodo, 75011, Paris, France

    mobilizon.fr/events/dd334825-5

  15. Dojo de programmation (vendredi) @ Shodo

    15 mai 2026, 19:00:00 UTC+02:00 - GMT+02:00 - Shodo, 75011, Paris, France

    mobilizon.fr/events/dd334825-5

  16. #tdd question:

    Do you write new tests when removing features? If so, how long do those tests live in your codebase?

  17. #tdd question:

    Do you write new tests when removing features? If so, how long do those tests live in your codebase?

  18. question:

    Do you write new tests when removing features? If so, how long do those tests live in your codebase?

  19. #tdd question:

    Do you write new tests when removing features? If so, how long do those tests live in your codebase?

  20. #tdd question:

    Do you write new tests when removing features? If so, how long do those tests live in your codebase?

  21. 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: javapro.io/2026/01/21/test-you

    #Java #TDD #MutationTesting #JUnit5

  22. 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: javapro.io/2026/01/21/test-you

    #Java #TDD #MutationTesting #JUnit5

  23. 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: javapro.io/2026/01/21/test-you

    #Java #TDD #MutationTesting #JUnit5

  24. 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: javapro.io/2026/01/21/test-you

    #Java #TDD #MutationTesting #JUnit5

  25. 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: javapro.io/2026/01/21/test-you

    #Java #TDD #MutationTesting #JUnit5

  26. In the AI era, we’re drifting into two extremes: rejecting AI entirely, or YOLO-ing it into everything. Both miss the point.

    A #UITest surfaced a subtle boundary violation (inconsistent device attributes, see below). This is the kind of issue a human eye can easily miss and this is where vigilance matters.

    Actually, #TDD has become a superpower again. Not just for safety, but for leverage:

    Make invalid states impossible, then let #AI operate within those constraints. #SoftwareEngineering

  27. In the AI era, we’re drifting into two extremes: rejecting AI entirely, or YOLO-ing it into everything. Both miss the point.

    A #UITest surfaced a subtle boundary violation (inconsistent device attributes, see below). This is the kind of issue a human eye can easily miss and this is where vigilance matters.

    Actually, #TDD has become a superpower again. Not just for safety, but for leverage:

    Make invalid states impossible, then let #AI operate within those constraints. #SoftwareEngineering

  28. In the AI era, we’re drifting into two extremes: rejecting AI entirely, or YOLO-ing it into everything. Both miss the point.

    A #UITest surfaced a subtle boundary violation (inconsistent device attributes, see below). This is the kind of issue a human eye can easily miss and this is where vigilance matters.

    Actually, #TDD has become a superpower again. Not just for safety, but for leverage:

    Make invalid states impossible, then let #AI operate within those constraints. #SoftwareEngineering

  29. We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.

    This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!

    xunit.net/releases/v3/4.0.0-pr
    xunit.net/releases/analyzers/2

    #DotNet #CSharp #FSharp #UnitTest #TDD #NativeAOT

  30. We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.

    This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!

    xunit.net/releases/v3/4.0.0-pr
    xunit.net/releases/analyzers/2

    #DotNet #CSharp #FSharp #UnitTest #TDD #NativeAOT

  31. We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.

    This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!

    xunit.net/releases/v3/4.0.0-pr
    xunit.net/releases/analyzers/2

    #DotNet #CSharp #FSharp #UnitTest #TDD #NativeAOT

  32. We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.

    This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!

    xunit.net/releases/v3/4.0.0-pr
    xunit.net/releases/analyzers/2

    #DotNet #CSharp #FSharp #UnitTest #TDD #NativeAOT

  33. We just shipped Core Framework v3 4.0.0-pre.108 and Analyzers 2.0.0-pre.51.

    This release adds new features, new analyzers, and fixed several bugs. We anticipate these being the final prerelease builds of this cycle. Please test thoroughly!

    xunit.net/releases/v3/4.0.0-pr
    xunit.net/releases/analyzers/2

    #DotNet #CSharp #FSharp #UnitTest #TDD #NativeAOT