<?xml version="1.0" encoding="UTF-8"?>
<!-- GENERATED by /update-blog from blog/*.md — do not hand-edit. Newest-first. -->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SYZYGY — Blog</title>
    <link>https://syz.sh/blog/</link>
    <atom:link href="https://syz.sh/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Field notes on integration testing, durable integration knowledge, deterministic execution, and keeping requirements, tests, and traceability aligned — from the team building SYZYGY.</description>
    <language>en</language>
    <lastBuildDate>Wed, 12 Aug 2026 09:00:00 GMT</lastBuildDate>

    <item>
      <title>We've been failing BDD for two decades — and the .feature file is the evidence</title>
      <link>https://syz.sh/blog/failing-bdd-for-two-decades</link>
      <guid isPermaLink="true">https://syz.sh/blog/failing-bdd-for-two-decades</guid>
      <pubDate>Wed, 12 Aug 2026 09:00:00 GMT</pubDate>
      <description>BDD promised behaviour a business person could read. Decades on, .feature files are test scripts in disguise. The fix is knowledge documents before technology.</description>
      <category>bdd</category>
      <category>cucumber</category>
      <category>gherkin</category>
      <category>living-documentation</category>
      <category>requirements-traceability</category>
      <category>knowledge-first</category>
    </item>

    <item>
      <title>We built our services on a shared contract — but never our tests</title>
      <link>https://syz.sh/blog/a-shared-contract-for-your-tests</link>
      <guid isPermaLink="true">https://syz.sh/blog/a-shared-contract-for-your-tests</guid>
      <pubDate>Thu, 09 Jul 2026 09:00:00 GMT</pubDate>
      <description>Services share a contract, so they compose across teams. Tests share nothing — so no team can reuse another's, and component tests break at integration.</description>
      <category>test-plugins</category>
      <category>test-library</category>
      <category>test-reuse</category>
      <category>test-unframework</category>
      <category>test-strategy</category>
    </item>

    <item>
      <title>When the engineer leaves, the integration knowledge leaves with them</title>
      <link>https://syz.sh/blog/when-the-engineer-leaves</link>
      <guid isPermaLink="true">https://syz.sh/blog/when-the-engineer-leaves</guid>
      <pubDate>Wed, 08 Jul 2026 09:00:00 GMT</pubDate>
      <description>When the one engineer who understood your integrations leaves, the knowledge leaves too. Keep integration test knowledge in version control instead of in people's heads.</description>
      <category>integration-knowledge</category>
      <category>knowledge-retention</category>
      <category>domain-knowledge</category>
      <category>requirements-traceability</category>
      <category>testing</category>
    </item>

  </channel>
</rss>
