<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Testing on Hardcode Consulting</title>
    <link>https://blog.hardcodeconsulting.tech/tags/testing/</link>
    <description>Recent content in Testing on Hardcode Consulting</description>
    <image>
      <title>Hardcode Consulting</title>
      <url>https://blog.hardcodeconsulting.tech/favicon.svg</url>
      <link>https://blog.hardcodeconsulting.tech/favicon.svg</link>
    </image>
    <generator>Hugo -- 0.167.0</generator>
    <language>en</language>
    <lastBuildDate>Sun, 09 Aug 2026 18:00:00 +0530</lastBuildDate>
    <atom:link href="https://blog.hardcodeconsulting.tech/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Day Two Security Features Cancelled Out</title>
      <link>https://blog.hardcodeconsulting.tech/post/when-two-security-features-collide/</link>
      <pubDate>Sun, 09 Aug 2026 18:00:00 +0530</pubDate>
      <guid>https://blog.hardcodeconsulting.tech/post/when-two-security-features-collide/</guid>
      <description>Session branching and per request signing were both correct. Shipped together they made the recovery path unreachable by the only client that needed it.</description>
    </item>
  </channel>
</rss>
