<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #testing</title>
    <link>/tags/testing/</link>
    <description>Recent bookmarks tagged #testing</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:47 +0000</lastBuildDate>
    <item>
      <title>Leave a failing test before you go on vacation - Freek Van der Herten&#39;s blog on Laravel, PHP and AI</title>
      <link>https://freek.dev/3156-leave-a-failing-test-before-you-go-on-vacation</link>
      <description>Every year I dread coming back from vacation not because of the work, but because I have no idea where I left off. A failing test, a well-written TODO, and a slow first day back are all you need to ease back in.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #coding #dev #testing #work&lt;/p&gt;</description>
      <pubDate>Fri, 10 Jul 2026 22:12:45 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38637</guid>
      <category>coding</category>
      <category>dev</category>
      <category>testing</category>
      <category>work</category>
    </item>
    <item>
      <title>That time it tried to delete all my tests — Massively Parallel Procrastination</title>
      <link>https://blog.fsck.com/2026/04/30/that-time-it-tried-to-delete-all-my-tests/</link>
      <description>When you&#39;re writing prompts, think about the model as a lazy pedant.&#xA;&#xA;How could it do something that&#39;s technically what you asked, but not at all what you wanted?&#xA;&#xA;Are you pushing it in a direction that&#39;s going to cause it to get desperate out and look for shortcuts?&#xA;&#xA;How could you clarify what you&#39;re asking to help the model do the right thing?&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ai #codegen #llms #testing&lt;/p&gt;</description>
      <pubDate>Thu, 30 Apr 2026 21:50:48 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38492</guid>
      <category>ai</category>
      <category>codegen</category>
      <category>llms</category>
      <category>testing</category>
      <enclosure url="https://links.lmorchard.com/static/5bf5af8631861a4291110e25d2a1005a.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>Red/green TDD - Agentic Engineering Patterns - Simon Willison&#39;s Weblog</title>
      <link>https://simonwillison.net/guides/agentic-engineering-patterns/red-green-tdd/#atom-everything</link>
      <description>Test-first development helps protect against both of these common mistakes, and also ensures a robust automated test suite that protects against future regressions. As projects grow the chance that a new change might break an existing feature grows with them. A comprehensive test suite is by far the most effective way to keep those features working.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #agents #codegen #llms #testing&lt;/p&gt;</description>
      <pubDate>Tue, 03 Mar 2026 22:51:11 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38358</guid>
      <category>agents</category>
      <category>codegen</category>
      <category>llms</category>
      <category>testing</category>
    </item>
    <item>
      <title>Verification-First Development • Buttondown</title>
      <link>https://buttondown.com/hillelwayne/archive/verification-first-development/</link>
      <description>before writing code, put in place some means of verifying that the code is correct, or at least have an idea of what you&#39;ll do.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #testing #tests #vfd&lt;/p&gt;</description>
      <pubDate>Tue, 18 Mar 2025 23:26:49 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29616</guid>
      <category>dev</category>
      <category>testing</category>
      <category>tests</category>
      <category>vfd</category>
    </item>
    <item>
      <title>Depth is all you need: how Antithesis crushes Gradius</title>
      <link>https://antithesis.com/blog/2025/gradius/</link>
      <description>Antithesis’ ability to play like a computer, not a human being, is central both to finding bugs and beating side-scrolling shooters.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #ai #antithesis #ml #nes #testing&lt;/p&gt;</description>
      <pubDate>Mon, 24 Feb 2025 04:20:20 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29640</guid>
      <category>ai</category>
      <category>antithesis</category>
      <category>ml</category>
      <category>nes</category>
      <category>testing</category>
      <enclosure url="https://links.lmorchard.com/static/7a595c70fb5814d48c7a7adb6f324d29.jpg" type="image/jpeg"></enclosure>
    </item>
    <item>
      <title>How to fix Storybook screenshot testing | Tiger Oakes</title>
      <link>https://tigeroakes.com/posts/storybook-test-runner-screenshots/</link>
      <description>As an alternative to Chromatic, I’ve been using Storybook’s Test Runner to power screenshot tests for Microsoft Loop. We configure the test runner to run in CI and take a screenshot of every story. However, the initial implementation based on the official Storybook docs was very flaky due to inconsistent screenshots of the same story. Here are some tips to reduce flakiness in your Storybook screenshot tests.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #css #html #react #storybook #testing #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 04 Dec 2024 22:02:41 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29774</guid>
      <category>css</category>
      <category>html</category>
      <category>react</category>
      <category>storybook</category>
      <category>testing</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Storybook Test sneak peek</title>
      <link>https://storybook.js.org/blog/storybook-test-sneak-peek/</link>
      <description>At Storybook, we believe there’s still hope. For months we’ve been building Storybook Test, a tool for fast, flake-free UI tests. And we’re finally ready to share it with you.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #components #storybook #testing #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 07 Nov 2024 19:30:01 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29901</guid>
      <category>components</category>
      <category>storybook</category>
      <category>testing</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Unit testing React components without a DOM – simonsmith.io – Portfolio and blog of a London based front-end web developer</title>
      <link>http://simonsmith.io/unit-testing-react-components-without-a-dom/?imm_mid=0d3af7&amp;cmp=em-web-na-na-newsltr_20150617</link>
      <description>the idea of shallow rendering is to instantiate a component and get the result of its render method, which is a ReactElement. From here you can do things like check its props and children and verify it works as expected.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apps #imported:pinboard #react #testing #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 18 Jun 2015 01:53:05 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:31582</guid>
      <category>apps</category>
      <category>imported:pinboard</category>
      <category>react</category>
      <category>testing</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Unit testing React components without a DOM – simonsmith.io – Portfolio and blog of a London based front-end web developer</title>
      <link>http://simonsmith.io/unit-testing-react-components-without-a-dom?cmp=em-web-na-na-newsltr_20150617&amp;imm_mid=0d3af7</link>
      <description>the idea of shallow rendering is to instantiate a component and get the result of its render method, which is a ReactElement. From here you can do things like check its props and children and verify it works as expected.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apps #react #testing #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 18 Jun 2015 01:53:05 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:25761</guid>
      <category>apps</category>
      <category>react</category>
      <category>testing</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Meet Runscope — Runscope Blog</title>
      <link>http://blog.runscope.com/posts/meet-runscope</link>
      <description>Tools that give application developers visibility into the conversations their apps are having with the services they rely on. Tools that make debugging and testing your API integrations as simple as any other line of code.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #dev #gluecon #imported:pinboard #integration #testing #webservices&lt;/p&gt;</description>
      <pubDate>Wed, 22 May 2013 23:39:10 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23669</guid>
      <category>apis</category>
      <category>dev</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>integration</category>
      <category>testing</category>
      <category>webservices</category>
    </item>
    <item>
      <title>M/M/c queue - Wikipedia, the free encyclopedia</title>
      <link>http://en.wikipedia.org/wiki/M/M/c_queue</link>
      <description>In queueing theory, the M/M/c queue is a multi-server queueing model.[1] In Kendall&#39;s notation it describes a system where arrivals form a single queue and are governed by a Poisson process, there are c servers and job service times are exponentially distributed.[2] It is a generalisation of the M/M/1 queue which considers only a single server. The model with infinitely many servers is the M/M/∞ queue.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #cloud #gluecon #imported:pinboard #operations #testing&lt;/p&gt;</description>
      <pubDate>Wed, 22 May 2013 23:27:34 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23667</guid>
      <category>cloud</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>operations</category>
      <category>testing</category>
    </item>
    <item>
      <title>geertj / mdc_queue</title>
      <link>https://github.com/geertj/mdc_queue</link>
      <description>Simulation of an M/D/c queue&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #gluecon #imported:pinboard #operations #queuing #testing&lt;/p&gt;</description>
      <pubDate>Wed, 22 May 2013 23:26:48 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23666</guid>
      <category>dev</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>operations</category>
      <category>queuing</category>
      <category>testing</category>
    </item>
    <item>
      <title>testling</title>
      <link>http://ci.testling.com/</link>
      <description>run your browser tests on every push&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #browser #imported:pinboard #javascript #testing #testling #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 04 Jan 2013 16:34:04 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32576</guid>
      <category>browser</category>
      <category>imported:pinboard</category>
      <category>javascript</category>
      <category>testing</category>
      <category>testling</category>
      <category>webdev</category>
    </item>
    <item>
      <title>testling</title>
      <link>http://ci.testling.com</link>
      <description>run your browser tests on every push&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #browser #javascript #testing #testling #webdev&lt;/p&gt;</description>
      <pubDate>Fri, 04 Jan 2013 16:34:04 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23003</guid>
      <category>browser</category>
      <category>javascript</category>
      <category>testing</category>
      <category>testling</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Using Travis-CI with Python and Django - David Cramer&#39;s Blog</title>
      <link>http://justcramer.com/2012/05/03/using-travis-ci/</link>
      <description>I’ve been using Travis-CI for a while now. Both my personal projects, and even several of the libraries we maintain at DISQUS rely on it for Continuous Integration. I figured it was about time to confess my undenying love for Travis, and throw up some notes about the defaults we use in our projects.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #django #imported:pinboard #python #testing #travisci&lt;/p&gt;</description>
      <pubDate>Wed, 02 Jan 2013 02:59:59 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32584</guid>
      <category>django</category>
      <category>imported:pinboard</category>
      <category>python</category>
      <category>testing</category>
      <category>travisci</category>
    </item>
  </channel>
</rss>
