<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rehearsal on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/rehearsal/</link><description>Recent content in Rehearsal on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Thu, 01 Oct 2026 08:00:00 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/rehearsal/index.xml" rel="self" type="application/rss+xml"/><item><title>Rehearse the deploy, not the test suite</title><link>https://startaitools.com/posts/rehearse-before-production-catches-what-tests-cant/</link><pubDate>Thu, 01 Oct 2026 08:00:00 -0600</pubDate><guid>https://startaitools.com/posts/rehearse-before-production-catches-what-tests-cant/</guid><description>&lt;h2 id="the-finding"&gt;The finding&lt;/h2&gt;
&lt;p&gt;A ten-scenario rehearsal on the dev box caught a real production-breaking bug before it left the staging network. The bug was a folder-permission mistake in the deploy script: the directory the database process needed to write to was created with the wrong owner, and the database would not have started on the VPS. The test suite had nothing to say about it. The rehearsal said it on attempt two.&lt;/p&gt;</description></item></channel></rss>