<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -46,21 +46,30 @@ app.
    #!sh
    rake tarantula:setup
 
-Assuming users must log in before accessing your application, update the integration test to use the
-authentication parameters necessary to log in to your app. (If your application does *not* require
-authentication, you can safely remove the first two lines of the test.)
-
-You will probably want to include all fixtures so that Tarantula has plenty of links to follow, giving
-your app maximum exposure to Tarantula's crawler.
-
-   require 'relevance/tarantula'
-
-   # in your test
-   def test_tarantula
-     post '/session', :login =&gt; 'kilgore', :password =&gt; 'trout'
-     follow_redirect!
-     tarantula_crawl(self)
-   end   
+Take a moment to familiarize yourself with the generated test. If parts of your application require
+login, update the test to make sure Tarantula can access those parts of your app.
+
+   require &quot;relevance/tarantula&quot;
+   
+   class TarantulaTest &lt; ActionController::IntegrationTest
+     # Load enough test data to ensure that there's a link to every page in your
+     # application. Doing so allows Tarantula to follow those links and crawl 
+     # every page.  For many applications, you can load a decent data set by
+     # loading all fixtures.
+     fixtures :all
+   
+     def test_tarantula
+       # If your application requires users to log in before accessing certain 
+       # pages, uncomment the lines below and update them to allow this test to
+       # log in to your application.  Doing so allows Tarantula to crawl the 
+       # pages that are only accessible to logged-in users.
+       # 
+       #   post '/session', :login =&gt; 'quentin', :password =&gt; 'monkey'
+       #   follow_redirect!
+       
+       tarantula_crawl(self)
+     end
+   end
 
 If you want to set custom options, you can get access to the crawler and set properties before running
 it. For example, this would turn on HTMLTidy.
@@ -70,6 +79,7 @@ it. For example, this would turn on HTMLTidy.
      assert_response :redirect
      assert_redirected_to '/'
      follow_redirect!
+
      t = tarantula_crawler(self)
      t.handlers &lt;&lt; Relevance::Tarantula::TidyHandler.new
      t.crawl '/'</diff>
      <filename>README.rdoc</filename>
    </modified>
    <modified>
      <diff>@@ -2,11 +2,21 @@ require &quot;#{File.dirname(__FILE__)}/../test_helper&quot;
 require &quot;relevance/tarantula&quot;
 
 class TarantulaTest &lt; ActionController::IntegrationTest
+  # Load enough test data to ensure that there's a link to every page in your
+  # application. Doing so allows Tarantula to follow those links and crawl 
+  # every page.  For many applications, you can load a decent data set by
+  # loading all fixtures.
   fixtures :all
 
   def test_tarantula
-    post '/session', :login =&gt; 'quentin', :password =&gt; 'monkey'
-    follow_redirect!
+    # If your application requires users to log in before accessing certain 
+    # pages, uncomment the lines below and update them to allow this test to
+    # log in to your application.  Doing so allows Tarantula to crawl the 
+    # pages that are only accessible to logged-in users.
+    # 
+    #   post '/session', :login =&gt; 'quentin', :password =&gt; 'monkey'
+    #   follow_redirect!
+    
     tarantula_crawl(self)
   end
 end</diff>
      <filename>template/tarantula_test.rb</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>e90b84775011f606715be081bfe2a02974b43e8d</id>
    </parent>
  </parents>
  <author>
    <name>Jason Rudolph</name>
    <email>github@jasonrudolph.com</email>
  </author>
  <url>http://github.com/relevance/tarantula/commit/8baaaf2fa8b69c53b2ad233576950e2aa7c04a14</url>
  <id>8baaaf2fa8b69c53b2ad233576950e2aa7c04a14</id>
  <committed-date>2009-01-16T18:03:34-08:00</committed-date>
  <authored-date>2009-01-16T18:03:34-08:00</authored-date>
  <message>Update the tarantula_test template ...

  - Include documentation inside the test template explaining how to set up
    the test case
  - Make the simple case simple: Comment out the authentication code by
    default.  This allows the developer to generate the test and immediately
    run it.
  - Update README to reflect new test template</message>
  <tree>6640a97bf2151d43b38fe31cb78648148aef8b18</tree>
  <committer>
    <name>Jason Rudolph</name>
    <email>github@jasonrudolph.com</email>
  </committer>
</commit>
