http://www.robertshowalter.com/articles/2007/06/23/autotest-fails-after-migration en-us 40 <p>If you generate a new model or run a migration that makes changes to your database, <a href="http://www.zenspider.com/ZSS/Products/ZenTest/">autotest</a> will probably start reporting errors.</p> <p>For instance, if you generate a new model, edit the migration and then <code>rake db:migrate</code>, you might see something like this:</p> <div class="typocode"><pre><code class="typocode_default ">ActiveRecord::StatementInvalid: Mysql::Error: #42S02Table 'sample_test.widgets' doesn't exist: DELETE FROM widgets</code></pre></div> <p>autotest is really smart, which is great. But this one trips it up a bit. The problem is that autotest is running your new <code>widget_test.rb</code>, which is trying to load your new Widget fixtures. However, <code>rake db:migrate</code> only affects your production database, not your test database.</p> <p>The fix is simple:</p> <ol> <li>Run <code>rake db:test:prepare</code>. This applies the current development schema to your test database.</li> <li>Press Ctrl-C (once) in your autotest window. That tells autotest to restart itself and run the full test suite.</li> </ol> Sat, 23 Jun 2007 20:15:00 -0400 urn:uuid:f8fa4454-3a99-4864-b919-c6f45a1c1172 Bob Showalter http://www.robertshowalter.com/articles/2007/06/23/autotest-fails-after-migration Rails