home.social

Search

967 results for “tdd_fellow”

  1. Was fun to chat here dev2next with Baruch Sadogursky from TuxCare on #VerboseMode about TDD, AI, and JitterTed's TDD Game (tdd.cards)

    #TDD #dev2next

    View it here: youtube.com/watch?v=O6WuOH4ZLIE

  2. Was fun to chat here dev2next with Baruch Sadogursky from TuxCare on #VerboseMode about TDD, AI, and JitterTed's TDD Game (tdd.cards)

    #TDD #dev2next

    View it here: youtube.com/watch?v=O6WuOH4ZLIE

  3. Was fun to chat here dev2next with Baruch Sadogursky from TuxCare on #VerboseMode about TDD, AI, and JitterTed's TDD Game (tdd.cards)

    #TDD #dev2next

    View it here: youtube.com/watch?v=O6WuOH4ZLIE

  4. Most testing advice sounds great until you try it on a real project.

    That’s why I use 4 axioms of testing that hold up in real-world codebases:

    1. You can’t test everything
    2. You can’t prove it’s bug-free
    3. Start early
    4. Bias is real

    Ask this before writing a test:
    **“What’s the purpose of this test in this context?”**

    If it doesn’t verify, protect, or document behavior/specs why write it?

    #SoftwareTesting #TDD #CleanCode #DevMindset #GoodEnoughTesting

  5. Test Driven Development: сначала тесты, потом реализация

    Для большинства разработчиков очевидно, что сначала должен появляться код, а только потом тесты для проверки работоспособности этого кода. Но в этой статье мы рассмотрим обратный процесс — Test Driven Development. В простом понимании это означает написание тестов перед написанием кода, но на самом деле этот подход гораздо шире. Тесты перед реализацией заставляют вас больше думать о том, что на самом деле ожидается, а «как» приходит позже, и «как» — это деталь реализации, которую можно изменить с помощью рефакторинга. В этой статье, написанной на основе публикации Rogério Chaves «The complete guide for TDD with LLMs» мы рассмотрим использование больших языковых моделей (LLM) для Test Driven Development.

    habr.com/ru/companies/otus/art

    #llmмодели #tdd #pytest #Тестирование_с_LLM #Test_Driven_Development

  6. Thank you to the lovely people at Pact - Smartbear, who sent me some awesome swag for my talk, Using Pact to Deploy Microservices with Confidence at GopherCon UK last summer.

    If you missed the talk you can watch the video here: youtube.com/watch?v=sibEijDJHGI

    #tdd #contractTesting

  7. 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.

    #CodeKata #TDD #LearnToCode #SoftwareCraftsmanship

  8. 1) Understand the domain
    2) Domain modelling (#ModelInCode)
    3) Let a test drive us (#TDD)
    4) Implement the controller
    5) Drive the core implementation by a test (TDD again)
    6) Extend the business logic facade (#HexagonalArchitecture)
    7) Implement the command
    8) Implement the event projection (#EventSourcing)
    9) Implement the database access (#OnionArchitecture)
    10) Release it (#CI_CD)
    11) See your changes at work (#REPL #FSI)

    With code samples in #dotnet

  9. On this #greenfriday, I'm happy to announce that my book still has the exact same price as yesterday, and the day before that, and the month before that, etc. ... Also, all the proceeds will still be donated to animal welfare organisations.

    leanpub.com/writing-maintainab

    #tdd #testdrivendevelopment #unittests #unittesting #softwaredesign

  10. New blog post! Let's continue to write a parser combinator library in Scala 3 à la @pchiusano and @runarorama 's Red book... but using TDD!

    blog.agilogy.com/2022-12-16-wr

  11. @emilybache 's newest video on dealing with #legacycode is really deep & high-end #tdd #ApprovalTesting !

    I learned a lot, thanks Emily!

    watch her video:
    youtube.com/watch?v=cKj5cz8uAO

  12. @emilybache 's newest video on dealing with #legacycode is really deep & high-end #tdd #ApprovalTesting !

    I learned a lot, thanks Emily!

    watch her video:
    youtube.com/watch?v=cKj5cz8uAO

  13. @emilybache 's newest video on dealing with #legacycode is really deep & high-end #tdd #ApprovalTesting !

    I learned a lot, thanks Emily!

    watch her video:
    youtube.com/watch?v=cKj5cz8uAO

  14. Code coverage metrics HURT application quality, especially when gating deployments, because they are a misleading target, prioritizing superficial goals over meaningful use-case validation. A focus on achieving coverage percentages detracts from real quality assurance, as developers write tests that do what the targets insist that they do, satisfy coverage metrics rather than ensuring comprehensive use-case functionality.

  15. QUnit 2.22.0 is out!

    ☑️ New `test.if()` and `module.if()` functions to facilitate conditional skipping.

    Changelog: github.com/qunitjs/qunit/blob/
    Download: qunitjs.com/intro/#release-cha
    Docs: qunitjs.com/api/QUnit/test.if/

  16. The journey to QUnit 3 has begun!

    Most projects require no changes to upgrade. It's the same easy-to-use API you know.

    If you use/maintain plugins, themes, or other integrations, minor changes might be needed. Take QUnit 3.0.0-alpha for a spin, and let us know about any surprises or issues!

    Changelog: github.com/qunitjs/qunit/blob/

    Much improved docs: qunitjs.com/intro/

    New theme design: github.com/qunitjs/qunit/pull/

    Matrix chat: app.element.io/#/room/#qunitjs

  17. QUnit 2.19.4

    Highlights since 2.19.0:
    ⏱ Faster assert.deepEqual() and QUnit.equiv() by @izelnakri and @krinkle.
    ⏱ Faster diffing when using config.noglobals.
    🐛 Fix memory release from last async test.
    🐛 Fix various CLI bugs.
    📝 Improve API examples and fix typos.

    Thanks Izel Nakri, Sergey Astapov, and others for their contributions.

    Details: github.com/qunitjs/qunit/blob/
    Download: qunitjs.com/intro/#release-cha

  18. I was not able to join todays Armakuni #teaming session but it should be a good one.

    They are practicing #tdd in #kotlin

    youtube.com/live/BulcKB8fSp0?f

  19. Although I don't have a comfortable #TestFirstProgramming / #tdd workflow yet for #jaq / #jq, a comfortable workflow is emerging in which I start by processing a single example, then generalize the algorithm incrementally.

    That's almost as good.

  20. Il a aussi parlé d'une méthodologie de développement que je ne connaissais pas : l'#ITL, qui n'a même pas de page Wikipédia (francophone ou anglophone). En gros, c'est du #TDD où on écrit le test après.

  21. Il a aussi parlé d'une méthodologie de développement que je ne connaissais pas : l'#ITL, qui n'a même pas de page Wikipédia (francophone ou anglophone). En gros, c'est du #TDD où on écrit le test après.

  22. Il a aussi parlé d'une méthodologie de développement que je ne connaissais pas : l'#ITL, qui n'a même pas de page Wikipédia (francophone ou anglophone). En gros, c'est du #TDD où on écrit le test après.

  23. "You need tests that don't break when you refactor. When you use dynamic mocks, tests tend to fail whenever you make changes in SUTs. Even though you have tests, they don't enable refactoring."

    #softwareengineering #tdd #fakes #vs #mocks

    blog.ploeh.dk/2022/10/17/stubs

  24. I enjoy my first steps in Emacs Lisp. It's interesting to learn about a tool I use everyday (Emacs) haha

    Still stuck with my first test !

    srfi64-mode on its way !

    #emacs #elisp #scheme #srfi64 #guile #testDrivenDevelopment #tdd #test

  25. We had a fun #TestDrivenDevelopment workshop at #PyConCZ23 today. Pair-programming, katas and practicing the craft of testing is always a great investment of time.

    #PyConCZ #TDD #testing