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.

Search results for tag #TDD

#refactoring boosted

[?]Leanpub » 🌐
@leanpub@mastodon.social

#refactoring boosted

[?]Leanpub » 🌐
@leanpub@mastodon.social

Leanpub book LAUNCH 🚀 The Other Half of Coding: What they Didn't Teach You by Max Guernsey, III

Watch here: youtu.be/lDwuiSwaCf4

    [?]Falk Appel » 🌐
    @FalkAppel@sueden.social


    I'm still looking for a new in .
    I offer () or whatever you name it and a lot other stuff. I wouldn't reject any role which I already had, eg. Architect, TeamLead, Product Owner etc...
    My skills reach from or pipelines, project setups or firefighting to and merging and splitting teams/departments and organising company wide initiatives.

      [?]Ted M. Young » 🌐
      @jitterted@sfba.social

      When figuring out what was needed for "find all events after a given checkpoint", that was on the Discovery/Design side of . Once I had that defined (an interface and 2 implementations), then I could move completely into implementation, using the tests to take safe steps.

        [?]Ted M. Young » 🌐
        @jitterted@sfba.social

        On my live coding stream today, when implementing the JDBC implementation of my Event Store, I talked about doing for Discovery and Design (learning about what the desired behavior should be), vs. implementing a known behavioral specification.

        jitterted.stream

          billwake boosted

          [?]Ted M. Young » 🌐
          @jitterted@sfba.social

          Remember that the “Red” (failing test) part of is the perfect time to make sure the failure message is useful, instead of the less than helpful “expected actual to not be null”.

            [?]dtanzer » 🌐
            @dtanzer@social.devteams.at

            I now have a GUI for my
            Will optimize the code a bit and try to test _some_ of the UI code with unit tests.

            Then I might record a video, since I did not yet find one on youtube where someone implements it in Rust using (if you know such a video, please forward it to me).

              [?]dtanzer » 🌐
              @dtanzer@social.devteams.at

              Another implementation of game-of-life, this time in and I tried to use some constraints:

              codeberg.org/dtanzer/game-of-l

              Didn't clean up the test file, that was not what I wanted to practice this time. Also, forgot to commit after each micro step during the cycle.

              And it's probably my last game-of-life for some time, since this year's global-day-of-code-retreat is over.

                [?]dtanzer » 🌐
                @dtanzer@social.devteams.at

                Made a first attempt of in - Feel free to roast my code, happy to hear feedback! It's just the "prime factors" - kata, though: codeberg.org/dtanzer/rust-play

                Also, should I use an assertion library? Found some, and "assert_eq!" seems not very powerful...

                  #agile boosted

                  [?]Thomas - NBA » 🌐
                  @nobsagile@mastodon.social

                  Fühlt sich Testing für euch auch oft wie eine Bremse an? 🐌 Die CI-Pipeline ist ewig rot, man schreibt Tests für Tests und am Ende liefert man trotzdem langsamer.

                  Das ist kein Sicherheitsnetz, das ist "Quality Theatre". Passiert, wenn Tests nur ein Ritual sind.

                  Automatisierte Tests sind nicht der Bremsklotz, sie sind euer Gaspedal. Wenn sie euch hindern, nutzt sie nicht.

                  Agilität braucht ein Sicherheitsnetz. Wie seht ihr das?

                    Mike Bowler boosted

                    [?]Sébastien Roccaserra 🐿️ » 🌐
                    @sroccaserra@mastodon.social

                    I've been teaching Test-Driven Development (TDD) for 6 months now, to 10 teams.

                    The feedback I have from these teams, 3 months after the sessions, is that of course they don't always use TDD, they use it sometimes. But most say that they now look at writing software differently.

                    I think they have integrated this way of "design is also in the smaller things", checking that it works all the time, and more communication inside and outside the team.

                    I'm so happy about these feedbacks!

                      [?]Jon Reid » 🌐
                      @qcoding@iosdev.space

                      Keep Your SwiftUI Tests Focused by Writing Them in English First qualitycoding.org/describe-tes

                      iOS Test-Driven Development
Describe Your Test in Plain English
Quality Coding with Jon Reid
Image of post-it note with test

                      Alt...iOS Test-Driven Development Describe Your Test in Plain English Quality Coding with Jon Reid Image of post-it note with test

                        [?]Wolfram wants peace » 🌐
                        @wolframkriesing@mastodontech.de

                        Last commit message: "Build the updates for the email, using . This would have been too hairy otherwise."

                        Makes me pretty happy. For one, that I found when I want TDD and two that I really get very satisfying results. Code is readable, as simple as I could do it (now) and it was fun and 🥁 🥁 🥁 QUICK!

                        when it's right, which is the hard part.

                          Ted M. Young boosted

                          [?]Ted M. Young » 🌐
                          @jitterted@sfba.social

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

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

                            [?]Christian Hujer » 🌐
                            @christianhujer@mastodon.social

                            AceUnit v3.0.0 is officially released!

                            Enjoy a new world of unit testing C with automatic test discovery!

                            github.com/christianhujer/aceu

                              [?]Jon Reid » 🌐
                              @qcoding@iosdev.space

                              Describe Your Test in Plain English qualitycoding.org/describe-tes

                              iOS Test-Driven Development
Describe Your Test in Plain English
Quality Coding with Jon Reid
Image of post-it note with test

                              Alt...iOS Test-Driven Development Describe Your Test in Plain English Quality Coding with Jon Reid Image of post-it note with test

                                [?]Jan Van Ryswyck » 🌐
                                @janvanryswyck@mastodon.social

                                When naming tests, avoid using technical names of functions/classes. When we encorporate the name of a function into the descriptive name of a test method, and the respective function is later renamed, then the description of the test becomes completely useless. A better approach is to describe the behaviour of the production code under test. That way we can refactor more confidently without rendering the names of our tests as obsolete.

                                  [?]is deeply, deeply sorry » 🌐
                                  @sleepyfox@hachyderm.io

                                  is about practice, "instead of reading the menu you eat the food".
                                  It's not about 'book learning', it is experiential. You can't study your way to expertise, you have to practice.
                                  The practice changes you, changes your mind, changes your way of working, changes the way you think. It is transformative.
                                  You don't need a mentor or coach for this, I didn't have one, but it does make it a lot quicker and easier to achieve competance.

                                    [?]alexboly » 🌐
                                    @alexboly@mastodon.social

                                    Just published: Doing the simplest thing that could possibly work often involves incremental thinking: the engineering practice of splitting a large problems into smaller problems so that their resolution grows into the solution that you are looking for. Let's see a definition and a few examples.
                                    mozaicworks.com/blog/examples-

                                      Ted M. Young boosted

                                      [?]Jan Van Ryswyck » 🌐
                                      @janvanryswyck@mastodon.social

                                      The best thing about TDD is not necessarily the tests thats we write, but rather the instant feedback that we get from the decisions that we make during coding sessions. Especially when those decisions are related to the design of the system that we're working on.

                                        Brian Marick boosted

                                        [?]Jan Van Ryswyck » 🌐
                                        @janvanryswyck@mastodon.social

                                        Assertion libraries can be considered as mini-DSL’s that make automated tests more readable. When a team of devs make their choice, they usually judge on API preference. While it’s very important to have readable tests, the API should never be the deciding factor. What truly separates a good assertion library is the quality of its failure messages. The more actionable these messages, the faster you’ll diagnose the cause of failing tests.

                                          Ted M. Young boosted

                                          [?]Jon Reid » 🌐
                                          @qcoding@iosdev.space

                                          Discover techniques advice for on this Swift Academy Podcast. Learn how the new Swift Testing framework can enhance TDD practices. qualitycoding.org/mastering-td

                                            [?]Jan Van Ryswyck » 🌐
                                            @janvanryswyck@mastodon.social

                                            Test doubles expose design flaws in the code. Developers usually tend to respond to the pain that this induces by blaming test doubles instead of interpreting these signals as an issue with the design. If solitary tests are amplifiers for design flaws, then test doubles will amplify these design flaws tenfold.

                                              Brian Marick boosted

                                              [?]Jan Van Ryswyck » 🌐
                                              @janvanryswyck@mastodon.social

                                              Reflecting on 25 years as a software developer—a milestone I reached last July—I’m struck by how much the industry has evolved. I’ve seen hypes rise and fall, technologies come and go. However, there’s one thing has remained a constant: the value of Extreme Programming. I’ve been fortunate enough to learn and study the core values and practices of XP early in my career. I can only say that it has paid dividends ever since, for which I'm more than grateful.

                                              (1/3)

                                                Ron Jeffries boosted

                                                [?]Danny Faught » 🌐
                                                @swalchemist@fosstodon.org

                                                Use Your Unit Tests, or Else
                                                Thoughts on one of things you should do before getting started with TDD.

                                                linkedin.com/pulse/use-your-un

                                                  [?]Jon Reid » 🌐
                                                  @qcoding@iosdev.space

                                                  Discover techniques advice for on this Swift Academy Podcast. Learn how the new Swift Testing framework can enhance TDD practices. qualitycoding.org/mastering-td

                                                    [?]jo.vaneyck » 🌐
                                                    @jovaneyck@mastodon.social

                                                    Can AI coding agents do Test-Driven Development (TDD) properly? They sure can!

                                                    In this week's video I take a look at two approaches: prompt engineering & using the tdd-guard library

                                                    We'll run an experiment and compare results:
                                                    Does it improve code/test quality?
                                                    What are other trade-offs?
                                                    How does tooling like tdd-guard work behind the covers?

                                                    📺 youtu.be/IVdYaVKuekk

                                                      [?]Jon Reid » 🌐
                                                      @qcoding@iosdev.space

                                                      Here's how I started test-driving a SwiftUI counter app… qualitycoding.org/tdd-where-do

                                                        2 ★ 1 ↺
                                                        Ted M. Young boosted

                                                        [?]Amitai Schleier » 🌐
                                                        @schmonz@schmonz.com

                                                        Do you know your way around the API? I'd love to add support for it in Greencently, my tiny extension. How you can help: https://github.com/schmonz/junit-greencently/issues/29

                                                        (if you'd like to)

                                                          0 ★ 1 ↺
                                                          GeePawHill boosted

                                                          [?]Amitai Schleier » 🌐
                                                          @schmonz@schmonz.com

                                                          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)