Render the file named in the outer-most example group description.

Closes #11.

features/view_specs/view_spec.feature

@@ -0,0 +1,53 @@
+Feature: view spec
+
+  View specs live in spec/views and render view templates in isolation.
+
+  Scenario: passing spec
+    Given a file named "spec/views/widgets/index.html.erb_spec.rb" with:
+      """
+      require "spec_helper"
+
+      describe "widgets/index.html.erb" do
+        it "displays all the widgets" do
+          assign(:widgets, [
+            stub_model(Widget, :name => "slicer"),
+            stub_model(Widget, :name => "dicer")
+          ])
+
+          render
+
+          response.should contain("slicer")
+          response.should contain("dicer")
+        end
+      end
+      """
+    When I run "rspec spec/views"
+    Then I should see "1 example, 0 failures"
+
+  Scenario: passing spec with before and nesting
+    Given a file named "spec/views/widgets/index.html.erb_spec.rb" with:
+      """
+      require "spec_helper"
+
+      describe "widgets/index.html.erb" do
+
+        context "with 2 widgets" do
+          before(:each) do
+            assign(:widgets, [
+              stub_model(Widget, :name => "slicer"),
+              stub_model(Widget, :name => "dicer")
+            ])
+          end
+
+          it "displays both widgets" do
+            render
+
+            response.should contain("slicer")
+            response.should contain("dicer")
+          end
+        end
+      end
+      """
+    When I run "rspec spec/views"
+    Then I should see "1 example, 0 failures"
+

lib/rspec/rails/example/view_example_group.rb

@@ -41,7 +41,10 @@ def response
   end
 
   def file_to_render
-    running_example.example_group.description
+    # TODO - this seems a bit invasive - need a better API from Rspec::Core
+    # to expose the top level description that is not a class (which is what
+    # comes from describes()).
+    running_example.example_group.before_ancestors.first.description
   end
 
   def controller_path