anchor.diff:    <%= link_to 'Flash message',
           :controller => 'Caterpillar::Session', :action => :flash_msg -%><br />
   
  -  <%= link_to 'Cookies and session',
  -        :controller => 'Caterpillar::Session', :action => :cookie -%><br />
  +</div>
   
  +
  +<h1>JUnit</h1>
  +
  +The JUnit tests are used for automatic testing and they output XML. 
  +
  +<div class="testContainer">
  +
  +  <%= link_to 'Session cookie',
  +        :controller => 'Caterpillar::Junit', :action => :session_cookie -%><br />
  +
  +  <%= link_to 'Redirect',
  +        :controller => 'Caterpillar::Junit', :action => :redirect -%><br />
  +
  +  <%= link_to 'Session cookies & redirect',
  +        :controller => 'Caterpillar::Junit', :action => :cookies_with_redirect -%><br />
  +
  +</div>
  +
  +
  +</div>
   </body>
  
positive.code: <body>
  <h1>
  Rails-portlet test bench
  </h1>
  <p style="font-size: 14px;">
  These are isolated test cases of the Rails-portlet. These cases cover the most common techniques used in dynamic web applications. The <%= link_to_exit_portlet 'source code', 'http://rails-portlet.rubyforge.org/svn/trunk/caterpillar/portlet_test_bench/' -%> can be used as a reference for using the same features in other Rails apps.
  </p>
  
  <h1>HTTP</h1>
  
    <%= link_to 'URL parameter passing',
          :controller => 'Caterpillar::HttpMethods', :action => :parameter  -%><br />
  
negative.code:   <%= link_to 'link_to :method => :post',
          :controller => 'Caterpillar::Js', :action => :link_to_post  -%><br />
  
  </div>
  
  
  <h1>CSS</h1>
  <div class="testContainer">
  
    <%= link_to 'Simple CSS',
          :controller => 'Caterpillar::Css', :action => :simple  -%><br />
  