#automatedtests — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #automatedtests, aggregated by home.social.
-
Getting the genie (as @kentbeck calls it) to perform #TDD (Test-Driven Development) is... interesting.
#TestDrivenDevelopment #Software #Programming #AutomatedTests #AI #LLM #AIAssistedDevelopment #VibeCoding #AugmentedCoding
-
Getting the genie (as @kentbeck calls it) to perform #TDD (Test-Driven Development) is... interesting.
#TestDrivenDevelopment #Software #Programming #AutomatedTests #AI #LLM #AIAssistedDevelopment #VibeCoding #AugmentedCoding
-
Getting the genie (as @kentbeck calls it) to perform #TDD (Test-Driven Development) is... interesting.
#TestDrivenDevelopment #Software #Programming #AutomatedTests #AI #LLM #AIAssistedDevelopment #VibeCoding #AugmentedCoding
-
Getting the genie (as @kentbeck calls it) to perform #TDD (Test-Driven Development) is... interesting.
#TestDrivenDevelopment #Software #Programming #AutomatedTests #AI #LLM #AIAssistedDevelopment #VibeCoding #AugmentedCoding
-
Getting the genie (as @kentbeck calls it) to perform #TDD (Test-Driven Development) is... interesting.
#TestDrivenDevelopment #Software #Programming #AutomatedTests #AI #LLM #AIAssistedDevelopment #VibeCoding #AugmentedCoding
-
Re: Emily Bache on Ward Cunningham’s Fearless Refactoring
When I was a younger developer, I thought I knew how to make code better by, as the kids would say today, following vibes. Much later, a coworker gave me a copy of Martin Fowler's Refactoring. I regret how long I put off reading it. Even later, I read Sandi Metz's 99 Bottles of OOP and learned just how safe refactoring could be. Fearless refactoring is a skill that must be learned, and it is almost a superpower! […]https://kerrick.blog/posts/2025/re-emily-bache-on-ward-cunninghams-fearless-refactoring/
-
Re: Emily Bache on Ward Cunningham’s Fearless Refactoring
When I was a younger developer, I thought I knew how to make code better by, as the kids would say today, following vibes. Much later, a coworker gave me a copy of Martin Fowler's Refactoring. I regret how long I put off reading it. Even later, I read Sandi Metz's 99 Bottles of OOP and learned just how safe refactoring could be. Fearless refactoring is a skill that must be learned, and it is almost a superpower! […]https://kerrick.blog/posts/2025/re-emily-bache-on-ward-cunninghams-fearless-refactoring/
-
Re: Emily Bache on Ward Cunningham’s Fearless Refactoring
When I was a younger developer, I thought I knew how to make code better by, as the kids would say today, following vibes. Much later, a coworker gave me a copy of Martin Fowler's Refactoring. I regret how long I put off reading it. Even later, I read Sandi Metz's 99 Bottles of OOP and learned just how safe refactoring could be. Fearless refactoring is a skill that must be learned, and it is almost a superpower! […]https://kerrick.blog/posts/2025/re-emily-bache-on-ward-cunninghams-fearless-refactoring/
-
Re: Emily Bache on Ward Cunningham’s Fearless Refactoring
When I was a younger developer, I thought I knew how to make code better by, as the kids would say today, following vibes. Much later, a coworker gave me a copy of Martin Fowler's Refactoring. I regret how long I put off reading it. Even later, I read Sandi Metz's 99 Bottles of OOP and learned just how safe refactoring could be. Fearless refactoring is a skill that must be learned, and it is almost a superpower! […]https://kerrick.blog/posts/2025/re-emily-bache-on-ward-cunninghams-fearless-refactoring/
-
Acceptance Tests and Unit Tests as Documents First, Tests Second
The real reason [acceptance tests and unit tests] aren’t redundant is that their primary function is not testing. The fact that they are tests is incidental. Unit tests and acceptance tests are documents first, and tests second. As my wife and I were listening to Uncle Bob's book on professionalism in software, this line surprised me. Maybe it's just because I don't understand tests as well as I'd like, but I had to stop and take note. He clarified exactly what he meant, too: […]https://kerrick.blog/posts/2025/acceptance-tests-and-unit-tests-as-documents-first-tests-second/
-
Acceptance Tests and Unit Tests as Documents First, Tests Second
The real reason [acceptance tests and unit tests] aren’t redundant is that their primary function is not testing. The fact that they are tests is incidental. Unit tests and acceptance tests are documents first, and tests second. As my wife and I were listening to Uncle Bob's book on professionalism in software, this line surprised me. Maybe it's just because I don't understand tests as well as I'd like, but I had to stop and take note. He clarified exactly what he meant, too: […]https://kerrick.blog/posts/2025/acceptance-tests-and-unit-tests-as-documents-first-tests-second/
-
Acceptance Tests and Unit Tests as Documents First, Tests Second
The real reason [acceptance tests and unit tests] aren’t redundant is that their primary function is not testing. The fact that they are tests is incidental. Unit tests and acceptance tests are documents first, and tests second. As my wife and I were listening to Uncle Bob's book on professionalism in software, this line surprised me. Maybe it's just because I don't understand tests as well as I'd like, but I had to stop and take note. He clarified exactly what he meant, too: […]https://kerrick.blog/posts/2025/acceptance-tests-and-unit-tests-as-documents-first-tests-second/
-
Acceptance Tests and Unit Tests as Documents First, Tests Second
The real reason [acceptance tests and unit tests] aren’t redundant is that their primary function is not testing. The fact that they are tests is incidental. Unit tests and acceptance tests are documents first, and tests second. As my wife and I were listening to Uncle Bob's book on professionalism in software, this line surprised me. Maybe it's just because I don't understand tests as well as I'd like, but I had to stop and take note. He clarified exactly what he meant, too: […]https://kerrick.blog/posts/2025/acceptance-tests-and-unit-tests-as-documents-first-tests-second/
-
Automated Tests as Waste vs. Needed
“How do you reconcile the lean view that tests are waste with the need for tests in software development?” Mary’s immediate response: “Unit tests are what let you stop the line.”
Dottie Acton, Foreword to Leading Lean Software Development: Results Are Not the Point by Mary and Tom Poppendieck
-
Automated Tests as Waste vs. Needed
Dottie Acton, Foreword, Leading Lean Software Development: Results Are Not the Point, by Mary and Tom Poppendieck“How do you reconcile the lean view that tests are waste with the need for tests in software development?” Mary’s immediate response: “Unit tests are what let you stop the line.”
-
Automated Tests as Waste vs. Needed
Dottie Acton, Foreword, Leading Lean Software Development: Results Are Not the Point, by Mary and Tom Poppendieck“How do you reconcile the lean view that tests are waste with the need for tests in software development?” Mary’s immediate response: “Unit tests are what let you stop the line.”
-
Automated Tests as Waste vs. Needed
I was a relative newbie to both agile and lean when I first met Mary and Tom Poppendieck at an Agile Conference in Salt Lake City in 2003, so of course I started our conversation with the question that had been bothering me: “How do you reconcile the lean view that tests are waste with the need for tests in software development?” Mary’s immediate response: “Unit tests are what let you stop the line.” Dottie Acton, Foreword to Leading Lean Software Development: Results Are Not the […]https://kerrick.blog/posts/2025/automated-tests-as-waste-vs-needed/
-
Automated Tests as Waste vs. Needed
“How do you reconcile the lean view that tests are waste with the need for tests in software development?” Mary’s immediate response: “Unit tests are what let you stop the line.”
Dottie Acton, Foreword to Leading Lean Software Development: Results Are Not the Point by Mary and Tom Poppendieck
-
Confessions of a Software Developer: No More Self-Censorship
I haven't published since April because I've been afraid. I also avoided social media, news aggregators, and discussion forums for months. I'm done letting fear stop me. What was I afraid of? In this post I detail every single thing I've avoided admitting on this blog. […]https://kerrick.blog/articles/2025/confessions-of-a-software-developer-no-more-self-censorship/
-
Confessions of a Software Developer: No More Self-Censorship
I haven't published since April because I've been afraid. I also avoided social media, news aggregators, and discussion forums for months. I'm done letting fear stop me. What was I afraid of? In this post I detail every single thing I've avoided admitting on this blog. […]https://kerrick.blog/articles/2025/confessions-of-a-software-developer-no-more-self-censorship/
-
Confessions of a Software Developer: No More Self-Censorship
I haven't published since April because I've been afraid. I also avoided social media, news aggregators, and discussion forums for months. I'm done letting fear stop me. What was I afraid of? In this post I detail every single thing I've avoided admitting on this blog. […]https://kerrick.blog/articles/2025/confessions-of-a-software-developer-no-more-self-censorship/
-
Confessions of a Software Developer: No More Self-Censorship
I haven't published since April because I've been afraid. I also avoided social media, news aggregators, and discussion forums for months. I'm done letting fear stop me. What was I afraid of? In this post I detail every single thing I've avoided admitting on this blog. […]https://kerrick.blog/articles/2025/confessions-of-a-software-developer-no-more-self-censorship/
-
Confessions of a Software Developer: No More Self-Censorship
I haven't published since April because I've been afraid. I also avoided social media, news aggregators, and discussion forums for months. I'm done letting fear stop me. What was I afraid of? In this post I detail every single thing I've avoided admitting on this blog. […]https://kerrick.blog/articles/2025/confessions-of-a-software-developer-no-more-self-censorship/
-
Come and hear me and @bdemers rant about testing next week!
-
Come and hear me and @bdemers rant about testing next week!
-
Come and hear me and @bdemers rant about testing next week!
-
Come and hear me and @bdemers rant about testing next week!
-
Come and hear me and @bdemers rant about testing next week!
-
Ship Software That Does Nothing
You should ship software that does nothing. Absolutely nothing. I'm not being cheeky about this. I have no hidden meaning. The very first thing you should deliver when you start a new web application is absolutely nothing. Many people will tell you to ship a minimum viable product. Others say to ship a prototype to get feedback. Not me. I think you should ship a blank page to your production servers on day one. […]https://kerrick.blog/long-form/advice/2025/ship-software-that-does-nothing/
-
Ship Software That Does Nothing
You should ship software that does nothing. Absolutely nothing. I'm not being cheeky about this. I have no hidden meaning. The very first thing you should deliver when you start a new web application is absolutely nothing. Many people will tell you to ship a minimum viable product. Others say to ship a prototype to get feedback. Not me. I think you should ship a blank page to your production servers on day one. […]https://kerrick.blog/articles/2025/ship-software-that-does-nothing/
-
Ship Software That Does Nothing
You should ship software that does nothing. Absolutely nothing. I'm not being cheeky about this. I have no hidden meaning. The very first thing you should deliver when you start a new web application is absolutely nothing. Many people will tell you to ship a minimum viable product. Others say to ship a prototype to get feedback. Not me. I think you should ship a blank page to your production servers on day one. […]https://kerrick.blog/long-form/advice/2025/ship-software-that-does-nothing/
-
Ship Software That Does Nothing
You should ship software that does nothing. Absolutely nothing. I'm not being cheeky about this. I have no hidden meaning. The very first thing you should deliver when you start a new web application is absolutely nothing. Many people will tell you to ship a minimum viable product. Others say to ship a prototype to get feedback. Not me. I think you should ship a blank page to your production servers on day one. […]https://kerrick.blog/articles/2025/ship-software-that-does-nothing/
-
If you use feature flags your automated tests are worthless unless you run them against every possible combination of feature flags.
#developer #software #development #dev #softwaredevelopment #programming #softwareengineering #engineering #webDev #testing #AutomatedTests #tdd #unittesting #tests #featureFlag #feature #flag
-
If you use feature flags your automated tests are worthless unless you run them against every possible combination of feature flags.
#developer #software #development #dev #softwaredevelopment #programming #softwareengineering #engineering #webDev #testing #AutomatedTests #tdd #unittesting #tests #featureFlag #feature #flag
-
If you use feature flags your automated tests are worthless unless you run them against every possible combination of feature flags.
#developer #software #development #dev #softwaredevelopment #programming #softwareengineering #engineering #webDev #testing #AutomatedTests #tdd #unittesting #tests #featureFlag #feature #flag
-
If you use feature flags your automated tests are worthless unless you run them against every possible combination of feature flags.
#developer #software #development #dev #softwaredevelopment #programming #softwareengineering #engineering #webDev #testing #AutomatedTests #tdd #unittesting #tests #featureFlag #feature #flag
-
If you use feature flags your automated tests are worthless unless you run them against every possible combination of feature flags.
#developer #software #development #dev #softwaredevelopment #programming #softwareengineering #engineering #webDev #testing #AutomatedTests #tdd #unittesting #tests #featureFlag #feature #flag
-
ideally, there is a Test Engineer or QA team that can either write the functional tests, or confirm that those being referred to are legitimate and sufficient.
It's just important that when something is a barrier between your feature code and shipping there should be someone responsible for helping the team keep it green.
#testEngineering #softwareEngineering #testEngineer #automatedTests #softwareTesting #testing #tests #software
-
ideally, there is a Test Engineer or QA team that can either write the functional tests, or confirm that those being referred to are legitimate and sufficient.
It's just important that when something is a barrier between your feature code and shipping there should be someone responsible for helping the team keep it green.
#testEngineering #softwareEngineering #testEngineer #automatedTests #softwareTesting #testing #tests #software
-
ideally, there is a Test Engineer or QA team that can either write the functional tests, or confirm that those being referred to are legitimate and sufficient.
It's just important that when something is a barrier between your feature code and shipping there should be someone responsible for helping the team keep it green.
#testEngineering #softwareEngineering #testEngineer #automatedTests #softwareTesting #testing #tests #software
-
ideally, there is a Test Engineer or QA team that can either write the functional tests, or confirm that those being referred to are legitimate and sufficient.
It's just important that when something is a barrier between your feature code and shipping there should be someone responsible for helping the team keep it green.
#testEngineering #softwareEngineering #testEngineer #automatedTests #softwareTesting #testing #tests #software
-
ideally, there is a Test Engineer or QA team that can either write the functional tests, or confirm that those being referred to are legitimate and sufficient.
It's just important that when something is a barrier between your feature code and shipping there should be someone responsible for helping the team keep it green.
#testEngineering #softwareEngineering #testEngineer #automatedTests #softwareTesting #testing #tests #software
-
Another day, another bug caught by automated tests.
I missed injecting an OpenAI API key per tenant to OpenAIEmbeddings().
When tests ran locally they would pass because I have the OPENAI_API_KEY environment variable set on my machine.
Tests in CI failed red because that environment is clean.
-
Another day, another bug caught by automated tests.
I missed injecting an OpenAI API key per tenant to OpenAIEmbeddings().
When tests ran locally they would pass because I have the OPENAI_API_KEY environment variable set on my machine.
Tests in CI failed red because that environment is clean.
-
Another day, another bug caught by automated tests.
I missed injecting an OpenAI API key per tenant to OpenAIEmbeddings().
When tests ran locally they would pass because I have the OPENAI_API_KEY environment variable set on my machine.
Tests in CI failed red because that environment is clean.
