<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Testomatica blog</title>
  <link>https://testomatica.com/blog/</link>
  <atom:link href="https://testomatica.com/blog/feed.xml" rel="self" type="application/rss+xml" />
  <description>Notes on testing at AI speed from the Testomatica Team.</description>
  <language>en-us</language>
  <item>
    <title>Early access is open. Here's what happens next</title>
    <link>https://testomatica.com/blog/early-access-is-open.html</link>
    <guid>https://testomatica.com/blog/early-access-is-open.html</guid>
    <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Company</category>
    <description>Testomatica is opening to a small group of early teams. What onboarding looks like, who it's for, and what's still rough.</description>
  </item>
  <item>
    <title>Halloween: the scariest bugs make no noise</title>
    <link>https://testomatica.com/blog/halloween-silent-bugs.html</link>
    <guid>https://testomatica.com/blog/halloween-silent-bugs.html</guid>
    <pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Culture</category>
    <description>A crash at least screams. The bugs that keep us up at night return 200 OK and look perfectly fine.</description>
  </item>
  <item>
    <title>Giving coding agents a QA teammate over MCP</title>
    <link>https://testomatica.com/blog/a-qa-teammate-for-coding-agents.html</link>
    <guid>https://testomatica.com/blog/a-qa-teammate-for-coding-agents.html</guid>
    <pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Product</category>
    <description>Coding agents can now ask Testomatica what a change will affect, which rules apply and which tests to run, before they write the code.</description>
  </item>
  <item>
    <title>Measuring 360° coverage instead of guessing it</title>
    <link>https://testomatica.com/blog/measuring-360-coverage.html</link>
    <guid>https://testomatica.com/blog/measuring-360-coverage.html</guid>
    <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>&quot;What did we test?&quot; deserves a real answer. Here's how a coverage map turns a vague feeling into a number.</description>
  </item>
  <item>
    <title>Every proven bug becomes a permanent test</title>
    <link>https://testomatica.com/blog/every-bug-becomes-a-test.html</link>
    <guid>https://testomatica.com/blog/every-bug-becomes-a-test.html</guid>
    <pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Product</category>
    <description>Agents explore, a referee proves, and the finding becomes regression coverage. Your safety net grows with every release.</description>
  </item>
  <item>
    <title>Field notes: our first dry run against a live staging site</title>
    <link>https://testomatica.com/blog/first-dry-run-on-staging.html</link>
    <guid>https://testomatica.com/blog/first-dry-run-on-staging.html</guid>
    <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Field notes</category>
    <description>Two dry runs, one laptop, one VPN. What the referee confirmed, what the agent got wrong, and what we're changing.</description>
  </item>
  <item>
    <title>An impact graph for code that agents write</title>
    <link>https://testomatica.com/blog/impact-graph-for-agent-code.html</link>
    <guid>https://testomatica.com/blog/impact-graph-for-agent-code.html</guid>
    <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Product</category>
    <description>A coding agent changes a SQL procedure. Which pages, rules and tests does that touch? We built a graph to answer that from the diff.</description>
  </item>
  <item>
    <title>Talk Like a Pirate Day: X marks the bug</title>
    <link>https://testomatica.com/blog/x-marks-the-bug.html</link>
    <guid>https://testomatica.com/blog/x-marks-the-bug.html</guid>
    <pubDate>Sat, 19 Sep 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Culture</category>
    <description>It's Talk Like a Pirate Day, so here's a bug report written like a treasure map. Turns out pirates had decent instincts about reproducible steps.</description>
  </item>
  <item>
    <title>Programmers' Day: the 256th day and a second pair of eyes</title>
    <link>https://testomatica.com/blog/programmers-day-second-pair-of-eyes.html</link>
    <guid>https://testomatica.com/blog/programmers-day-second-pair-of-eyes.html</guid>
    <pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Culture</category>
    <description>Programmers' Day falls on day 256, two to the eighth. A small celebration of the people who write code, and of the habit of asking someone else to look.</description>
  </item>
  <item>
    <title>Why we built on Playwright, and why you can leave us anytime</title>
    <link>https://testomatica.com/blog/why-we-built-on-playwright.html</link>
    <guid>https://testomatica.com/blog/why-we-built-on-playwright.html</guid>
    <pubDate>Thu, 03 Sep 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>Every test Testomatica writes is a plain Playwright test in TypeScript. You can run it without us, keep it if you leave, and read it like any other code.</description>
  </item>
  <item>
    <title>The release gate: when a test system is allowed to say stop</title>
    <link>https://testomatica.com/blog/when-a-test-system-says-stop.html</link>
    <guid>https://testomatica.com/blog/when-a-test-system-says-stop.html</guid>
    <pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Product</category>
    <description>A production deploy asks one question: go, stop, or ask a human? Here's when we think a test system has earned the right to answer stop.</description>
  </item>
  <item>
    <title>A confidence score you can calculate</title>
    <link>https://testomatica.com/blog/confidence-you-can-calculate.html</link>
    <guid>https://testomatica.com/blog/confidence-you-can-calculate.html</guid>
    <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Product</category>
    <description>We don't ask the model how sure it is. Our confidence score is three numbers multiplied together, and you can check the math yourself.</description>
  </item>
  <item>
    <title>Evidence on every run, even the green ones</title>
    <link>https://testomatica.com/blog/evidence-on-every-run.html</link>
    <guid>https://testomatica.com/blog/evidence-on-every-run.html</guid>
    <pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Product</category>
    <description>A failing run without evidence is an argument. A passing run without evidence is a guess. Here's what we save on every attempt, and for how long.</description>
  </item>
  <item>
    <title>Staging is not fake production</title>
    <link>https://testomatica.com/blog/staging-is-not-production.html</link>
    <guid>https://testomatica.com/blog/staging-is-not-production.html</guid>
    <pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Methodology</category>
    <description>Staging has real-looking data but none of the real traffic. The rules we follow so tests on staging tell the truth instead of telling stories.</description>
  </item>
  <item>
    <title>SysAdmin Day: thank you for keeping staging alive</title>
    <link>https://testomatica.com/blog/sysadmin-day-staging.html</link>
    <guid>https://testomatica.com/blog/sysadmin-day-staging.html</guid>
    <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Culture</category>
    <description>The last Friday of July is SysAdmin Day. A thank-you to the people who keep staging running, and a promise about how our tests will treat it.</description>
  </item>
  <item>
    <title>Budgets, not hopes: keeping agent spend predictable</title>
    <link>https://testomatica.com/blog/budgets-not-hopes.html</link>
    <guid>https://testomatica.com/blog/budgets-not-hopes.html</guid>
    <pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>Agent exploration costs money every step. We cap it per run and per day, and when the money's gone, agents stop and the deterministic tests keep going.</description>
  </item>
  <item>
    <title>Read the diff before you read the page</title>
    <link>https://testomatica.com/blog/read-the-diff-first.html</link>
    <guid>https://testomatica.com/blog/read-the-diff-first.html</guid>
    <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Product</category>
    <description>An agent exploring a whole store at random wastes most of its time. Ours starts with the diff and the ticket, then decides where to look.</description>
  </item>
  <item>
    <title>Seven business rules every online store should check on every deploy</title>
    <link>https://testomatica.com/blog/rules-every-store-should-check.html</link>
    <guid>https://testomatica.com/blog/rules-every-store-should-check.html</guid>
    <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>Seven checks that hold for almost any online store, why each one matters, and why every rule has to catch a broken page before it can block a release.</description>
  </item>
  <item>
    <title>Declaring independence from the manual regression checklist</title>
    <link>https://testomatica.com/blog/independence-from-the-checklist.html</link>
    <guid>https://testomatica.com/blog/independence-from-the-checklist.html</guid>
    <pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Opinion</category>
    <description>The manual regression checklist did its job for years. On the Fourth of July, a few thoughts on what should replace it, and what shouldn't.</description>
  </item>
  <item>
    <title>An infrastructure failure is not a test failure</title>
    <link>https://testomatica.com/blog/infra-failure-is-not-a-test-failure.html</link>
    <guid>https://testomatica.com/blog/infra-failure-is-not-a-test-failure.html</guid>
    <pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>When the VPN drops or the model provider is down, nothing is wrong with your product. Our design keeps those two kinds of red very far apart.</description>
  </item>
  <item>
    <title>Father's Day: fix it once, fix it for good</title>
    <link>https://testomatica.com/blog/fathers-day-fix-it-once.html</link>
    <guid>https://testomatica.com/blog/fathers-day-fix-it-once.html</guid>
    <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Culture</category>
    <description>A dripping kitchen faucet, a patient dad, and the testing habit we keep coming back to: when you fix something, make sure it stays fixed.</description>
  </item>
  <item>
    <title>First sketches: a browser, a model and a loop</title>
    <link>https://testomatica.com/blog/a-browser-a-model-and-a-loop.html</link>
    <guid>https://testomatica.com/blog/a-browser-a-model-and-a-loop.html</guid>
    <pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>Our first rough prototype of an exploring agent is small: a handful of browser tools, a model, and a log a referee can replay without AI.</description>
  </item>
  <item>
    <title>Why our referee never uses AI</title>
    <link>https://testomatica.com/blog/why-our-referee-never-uses-ai.html</link>
    <guid>https://testomatica.com/blog/why-our-referee-never-uses-ai.html</guid>
    <pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Product</category>
    <description>The part of Testomatica that decides whether a finding is real has no model in it. That's on purpose, and here's why.</description>
  </item>
  <item>
    <title>Oracles, ranked: how we decide what counts as a bug</title>
    <link>https://testomatica.com/blog/oracles-ranked.html</link>
    <guid>https://testomatica.com/blog/oracles-ranked.html</guid>
    <pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Methodology</category>
    <description>Not every reason to call something broken is equally trustworthy. Here's the order we trust them in, with one store example for each.</description>
  </item>
  <item>
    <title>What automated accessibility scans can't see</title>
    <link>https://testomatica.com/blog/what-accessibility-scans-cant-see.html</link>
    <guid>https://testomatica.com/blog/what-accessibility-scans-cant-see.html</guid>
    <pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Quality</category>
    <description>What axe-core and WCAG 2.2 rules catch reliably, and the parts that still need a person with a keyboard and a screen reader.</description>
  </item>
  <item>
    <title>Quarantine first: how a new test earns its place in the gate</title>
    <link>https://testomatica.com/blog/quarantine-first.html</link>
    <guid>https://testomatica.com/blog/quarantine-first.html</guid>
    <pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>A new test doesn't block a release on day one. It has to prove it's stable first, and &quot;ten green runs&quot; isn't enough proof.</description>
  </item>
  <item>
    <title>Mother's Day: &quot;did you check it twice?&quot;</title>
    <link>https://testomatica.com/blog/mothers-day-check-it-twice.html</link>
    <guid>https://testomatica.com/blog/mothers-day-check-it-twice.html</guid>
    <pubDate>Sun, 10 May 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Culture</category>
    <description>A small Mother's Day story about a stove, a front door, and the oldest verification habit any of us learned.</description>
  </item>
  <item>
    <title>May Day: the QA work we want to automate, and the part we don't</title>
    <link>https://testomatica.com/blog/may-day-the-work-we-automate.html</link>
    <guid>https://testomatica.com/blog/may-day-the-work-we-automate.html</guid>
    <pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Opinion</category>
    <description>May Day is about work and the people who do it. A good moment to be clear about which parts of QA we want machines to take, and which belong to people.</description>
  </item>
  <item>
    <title>Earth Day: the greenest test is the one that never calls a model</title>
    <link>https://testomatica.com/blog/earth-day-greenest-test.html</link>
    <guid>https://testomatica.com/blog/earth-day-greenest-test.html</guid>
    <pubDate>Wed, 22 Apr 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>Model calls cost money and energy. Most testing doesn't need one. A short note on why our regression runs with no LLM at all.</description>
  </item>
  <item>
    <title>The coverage universe: mapping everything worth testing</title>
    <link>https://testomatica.com/blog/the-coverage-universe.html</link>
    <guid>https://testomatica.com/blog/the-coverage-universe.html</guid>
    <pubDate>Thu, 16 Apr 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>Code coverage tells you which lines ran. It can't tell you whether anyone checked the checkout on a slow phone. So we're drawing a bigger map.</description>
  </item>
  <item>
    <title>Session-based test management, but for agents</title>
    <link>https://testomatica.com/blog/session-based-testing-for-agents.html</link>
    <guid>https://testomatica.com/blog/session-based-testing-for-agents.html</guid>
    <pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Methodology</category>
    <description>Charters, time boxes and debriefs were invented to make human exploration accountable. They turn out to be exactly what an AI explorer needs too.</description>
  </item>
  <item>
    <title>April Fools: bugs that look like jokes until they aren't</title>
    <link>https://testomatica.com/blog/bugs-that-look-like-jokes.html</link>
    <guid>https://testomatica.com/blog/bugs-that-look-like-jokes.html</guid>
    <pubDate>Wed, 01 Apr 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Culture</category>
    <description>Some bugs are so absurd they read like a prank. That's exactly why they slip through. A short tour of the funny ones and why we check for them.</description>
  </item>
  <item>
    <title>Risk scores are for sorting, not for budgeting</title>
    <link>https://testomatica.com/blog/risk-is-for-sorting.html</link>
    <guid>https://testomatica.com/blog/risk-is-for-sorting.html</guid>
    <pubDate>Wed, 25 Mar 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Methodology</category>
    <description>Likelihood times impact is a fine way to decide what to test first. It's a bad way to decide what to skip. Here's how we use it.</description>
  </item>
  <item>
    <title>Metamorphic testing, explained with a shopping cart</title>
    <link>https://testomatica.com/blog/metamorphic-testing-shopping-cart.html</link>
    <guid>https://testomatica.com/blog/metamorphic-testing-shopping-cart.html</guid>
    <pubDate>Thu, 19 Mar 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Methodology</category>
    <description>You often can't say what the right answer is. You can say how two answers must relate. That idea is behind a whole family of our checks.</description>
  </item>
  <item>
    <title>Pi Day math: why we replay three times and accept two</title>
    <link>https://testomatica.com/blog/pi-day-two-out-of-three.html</link>
    <guid>https://testomatica.com/blog/pi-day-two-out-of-three.html</guid>
    <pubDate>Sat, 14 Mar 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Methodology</category>
    <description>Pi starts with a 3, and so does our referee. A short, friendly walk through the math behind accepting a finding at 2 out of 3 replays.</description>
  </item>
  <item>
    <title>The testers who taught us how to explore</title>
    <link>https://testomatica.com/blog/the-testers-who-taught-us-to-explore.html</link>
    <guid>https://testomatica.com/blog/the-testers-who-taught-us-to-explore.html</guid>
    <pubDate>Sun, 08 Mar 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Culture</category>
    <description>For International Women's Day, a thank-you to three testers whose books shaped how we think about exploration and whole-team quality.</description>
  </item>
  <item>
    <title>Personas are browser settings, not role-play</title>
    <link>https://testomatica.com/blog/personas-are-browser-settings.html</link>
    <guid>https://testomatica.com/blog/personas-are-browser-settings.html</guid>
    <pubDate>Tue, 24 Feb 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>Telling a model to pretend it's on a slow phone doesn't make the network slow. Why our personas are configuration first and character second.</description>
  </item>
  <item>
    <title>Why the LLM should suggest, and code should decide</title>
    <link>https://testomatica.com/blog/llm-suggests-code-decides.html</link>
    <guid>https://testomatica.com/blog/llm-suggests-code-decides.html</guid>
    <pubDate>Thu, 19 Feb 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Methodology</category>
    <description>AI bug verdicts are right about one time in four. Here's the setup that keeps AI useful without flooding you with false alarms.</description>
  </item>
  <item>
    <title>A love letter to deterministic tests</title>
    <link>https://testomatica.com/blog/love-letter-to-deterministic-tests.html</link>
    <guid>https://testomatica.com/blog/love-letter-to-deterministic-tests.html</guid>
    <pubDate>Sat, 14 Feb 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Opinion</category>
    <description>Everyone's excited about AI agents. On Valentine's Day, we'd like to say a few kind words about the boring tests that actually hold things together.</description>
  </item>
  <item>
    <title>Checking vs. testing: the distinction that shaped our design</title>
    <link>https://testomatica.com/blog/checking-vs-testing.html</link>
    <guid>https://testomatica.com/blog/checking-vs-testing.html</guid>
    <pubDate>Thu, 05 Feb 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Methodology</category>
    <description>Some work in QA is checking, some is testing, and mixing them up is how AI tools end up crying wolf. How the distinction shaped our design.</description>
  </item>
  <item>
    <title>Data Privacy Day: what our test agents are never allowed to see</title>
    <link>https://testomatica.com/blog/data-privacy-day.html</link>
    <guid>https://testomatica.com/blog/data-privacy-day.html</guid>
    <pubDate>Wed, 28 Jan 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Security</category>
    <description>A testing agent that can see everything is a liability. These are the privacy rules we wrote down before writing any code.</description>
  </item>
  <item>
    <title>Blue Monday, red builds: the real cost of flaky tests</title>
    <link>https://testomatica.com/blog/blue-monday-red-builds.html</link>
    <guid>https://testomatica.com/blog/blue-monday-red-builds.html</guid>
    <pubDate>Mon, 19 Jan 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Engineering</category>
    <description>A one percent flake rate sounds harmless. Across 150 tests, it blocks most deploys. Here's the math, and what one retry does to it.</description>
  </item>
  <item>
    <title>What we learned reading 40 papers on AI testing</title>
    <link>https://testomatica.com/blog/forty-papers-on-ai-testing.html</link>
    <guid>https://testomatica.com/blog/forty-papers-on-ai-testing.html</guid>
    <pubDate>Tue, 13 Jan 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Research</category>
    <description>Two weeks, about forty papers and a lot of coffee. Here's what changed our minds about AI testing, and what didn't.</description>
  </item>
  <item>
    <title>The verification gap nobody budgets for</title>
    <link>https://testomatica.com/blog/the-verification-gap.html</link>
    <guid>https://testomatica.com/blog/the-verification-gap.html</guid>
    <pubDate>Wed, 07 Jan 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Opinion</category>
    <description>Teams pay for coding agents and CI minutes. Almost nobody has a line item for checking what those agents produce.</description>
  </item>
  <item>
    <title>New year, same bugs: why we're building Testomatica</title>
    <link>https://testomatica.com/blog/new-year-same-bugs.html</link>
    <guid>https://testomatica.com/blog/new-year-same-bugs.html</guid>
    <pubDate>Thu, 01 Jan 2026 00:00:00 GMT</pubDate>
    <author>hello@testomatica.com (Testomatica Team)</author>
    <category>Company</category>
    <description>Code got faster. Checking it didn't. A new year, a small team, and the question we couldn't stop asking over the holidays.</description>
  </item>
</channel>
</rss>
