<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Testing on unweb.org</title>
    <link>https://unweb.org/tags/testing/</link>
    <description>Recent content in Testing on unweb.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://unweb.org/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Unweb Was Tested to Prove Nothing Carries Over Between Strangers</title>
      <link>https://unweb.org/how-unweb-was-tested-to-prove-nothing-carries-over-between-strangers/</link>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://unweb.org/how-unweb-was-tested-to-prove-nothing-carries-over-between-strangers/</guid>
      <description>&lt;p&gt;Unweb makes one promise above the rest: nothing carries over. Not between two strangers open at once, not from a closed stranger to a new one, not into your everyday browser, and nothing stays on disk once a stranger closes. A promise like that is easy to state and easy to break by accident, so the tests don&amp;rsquo;t take Unweb&amp;rsquo;s word for anything.&lt;/p&gt;&#xA;&lt;p&gt;The self-test runs the real app, on the system&amp;rsquo;s own web engine, against small web servers on the same machine. One plays a site at 127.0.0.1, another plays a third party at localhost, which counts as a different site. Every request they receive is logged with its cookies, and with any cached ID the browser sends back. Those logs decide each check.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Seeing Both Sides of a Checkout AB Test at Once</title>
      <link>https://unweb.org/seeing-both-sides-of-a-checkout-ab-test-at-once/</link>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://unweb.org/seeing-both-sides-of-a-checkout-ab-test-at-once/</guid>
      <description>&lt;p&gt;A site owner runs a test. Half the visitors get the old checkout, half get a new one with a lower price and a different button. Then someone asks what version B actually looks like on the live site, and nobody on the team can show them, because their browsers were sorted into A weeks ago and the cookie keeps them there.&lt;/p&gt;&#xA;&lt;p&gt;The usual fixes are a private window, then another, or clearing cookies over and over until the coin lands the other way. Each new try forgets the one before, so you never see the two side by side.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
