<?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 RenderCache.com</title>
    <link>https://rendercache.com/tags/testing/</link>
    <description>Recent content in Testing on RenderCache.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rendercache.com/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How RenderCache Is Tested</title>
      <link>https://rendercache.com/how-it-is-tested/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rendercache.com/how-it-is-tested/</guid>
      <description>&lt;p&gt;RenderCache makes a few promises that matter more than any feature. A crawler never waits for Chrome. A failed refresh never throws away a good page. A page with a cookie never ends up in a shared snapshot. Each promise has a test that tries to break it, and those tests run on every change, on Linux, macOS and Windows, with a real Chrome.&lt;/p&gt;&#xA;&lt;p&gt;The figures below come from the run behind 0.2.0. They&amp;rsquo;re copied from the &lt;a href=&#34;https://github.com/rendercache/rendercache/tree/main/test/results&#34;&gt;recorded results&lt;/a&gt; in the repository, which a script writes from the CI run, so nobody types them in.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
