<h1>Introduction</h1> <p>Usually, when deployed into an existing infrastructure, there is a need to create additional utilities to assist the test writer. These could include specialized mock objects, or simply bootstrap code that is required to properly initialize the environment. It&#8217;s important these files and environments get loaded before any main testing begins. To help facilitate this, an addon system exists.</p> <h1>Adding an Addon</h1> <p>An addon gets placed inside of the <code>/addons</code> directory. Only files immediately under <code>/addons</code> ending in <code>.php</code> are considered valid addons. In a complex addon, it is reccomended to hide your additional files one level deeper:</p> <pre><code> addons/ |- myaddon/ | |- myaddon_supplement.php | |- another_file.php |- myaddon.php </code></pre> <p>By the time the addon is reached, the entire SnapTest environment is available.</p> 2009-11-26T00:47:04-08:00 270410 extending-snaptest-with-addons 1880 2009-07-19T16:07:54-07:00 1795