Move documentation to the correct place

The documentation needs to be above the method to correctly document the
method.

1 files changed, 72 insertions, 72 deletions

diff --git a/actionpack/lib/action_dispatch/system_test_case.rb b/actionpack/lib/action_dispatch/system_test_case.rb
index 99c2be0a35..70a5b75781 100644
--- a/actionpack/lib/action_dispatch/system_test_case.rb
+++ b/actionpack/lib/action_dispatch/system_test_case.rb
@@ -7,79 +7,79 @@ require "action_dispatch/system_testing/test_helpers/screenshot_helper"
 require "action_dispatch/system_testing/test_helpers/setup_and_teardown"
 
 module ActionDispatch
+  # = System Testing
+  #
+  # System tests let you test applications in the browser. Because system
+  # tests use a real browser experience, you can test all of your JavaScript
+  # easily from your test suite.
+  #
+  # To create a system test in your application, extend your test class
+  # from <tt>ApplicationSystemTestCase</tt>. System tests use Capybara as a
+  # base and allow you to configure the settings through your
+  # <tt>application_system_test_case.rb</tt> file that is generated with a new
+  # application or scaffold.
+  #
+  # Here is an example system test:
+  #
+  #   require 'application_system_test_case'
+  #
+  #   class Users::CreateTest < ApplicationSystemTestCase
+  #     test "adding a new user" do
+  #       visit users_path
+  #       click_on 'New User'
+  #
+  #       fill_in 'Name', with: 'Arya'
+  #       click_on 'Create User'
+  #
+  #       assert_text 'Arya'
+  #     end
+  #   end
+  #
+  # When generating an application or scaffold, an +application_system_test_case.rb+
+  # file will also be generated containing the base class for system testing.
+  # This is where you can change the driver, add Capybara settings, and other
+  # configuration for your system tests.
+  #
+  #   require "test_helper"
+  #
+  #   class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
+  #     driven_by :selenium, using: :chrome, screen_size: [1400, 1400]
+  #   end
+  #
+  # By default, <tt>ActionDispatch::SystemTestCase</tt> is driven by the
+  # Selenium driver, with the Chrome browser, and a browser size of 1400x1400.
+  #
+  # Changing the driver configuration options are easy. Let's say you want to use
+  # the Firefox browser instead of Chrome. In your +application_system_test_case.rb+
+  # file add the following:
+  #
+  #   require "test_helper"
+  #
+  #   class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
+  #     driven_by :selenium, using: :firefox
+  #   end
+  #
+  # +driven_by+ has a required argument for the driver name. The keyword
+  # arguments are +:using+ for the browser and +:screen_size+ to change the
+  # size of the browser screen. These two options are not applicable for
+  # headless drivers and will be silently ignored if passed.
+  #
+  # To use a headless driver, like Poltergeist, update your Gemfile to use
+  # Poltergeist instead of Selenium and then declare the driver name in the
+  # +application_system_test_case.rb+ file. In this case you would leave out the +:using+
+  # option because the driver is headless.
+  #
+  #   require "test_helper"
+  #   require "capybara/poltergeist"
+  #
+  #   class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
+  #     driven_by :poltergeist
+  #   end
+  #
+  # Because <tt>ActionDispatch::SystemTestCase</tt> is a shim between Capybara
+  # and Rails, any driver that is supported by Capybara is supported by system
+  # tests as long as you include the required gems and files.
   class SystemTestCase < IntegrationTest
-    # = System Testing
-    #
-    # System tests let you test applications in the browser. Because system
-    # tests use a real browser experience, you can test all of your JavaScript
-    # easily from your test suite.
-    #
-    # To create a system test in your application, extend your test class
-    # from <tt>ApplicationSystemTestCase</tt>. System tests use Capybara as a
-    # base and allow you to configure the settings through your
-    # <tt>application_system_test_case.rb</tt> file that is generated with a new
-    # application or scaffold.
-    #
-    # Here is an example system test:
-    #
-    #   require 'application_system_test_case'
-    #
-    #   class Users::CreateTest < ApplicationSystemTestCase
-    #     test "adding a new user" do
-    #       visit users_path
-    #       click_on 'New User'
-    #
-    #       fill_in 'Name', with: 'Arya'
-    #       click_on 'Create User'
-    #
-    #       assert_text 'Arya'
-    #     end
-    #   end
-    #
-    # When generating an application or scaffold, an +application_system_test_case.rb+
-    # file will also be generated containing the base class for system testing.
-    # This is where you can change the driver, add Capybara settings, and other
-    # configuration for your system tests.
-    #
-    #   require "test_helper"
-    #
-    #   class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
-    #     driven_by :selenium, using: :chrome, screen_size: [1400, 1400]
-    #   end
-    #
-    # By default, <tt>ActionDispatch::SystemTestCase</tt> is driven by the
-    # Selenium driver, with the Chrome browser, and a browser size of 1400x1400.
-    #
-    # Changing the driver configuration options are easy. Let's say you want to use
-    # the Firefox browser instead of Chrome. In your +application_system_test_case.rb+
-    # file add the following:
-    #
-    #   require "test_helper"
-    #
-    #   class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
-    #     driven_by :selenium, using: :firefox
-    #   end
-    #
-    # +driven_by+ has a required argument for the driver name. The keyword
-    # arguments are +:using+ for the browser and +:screen_size+ to change the
-    # size of the browser screen. These two options are not applicable for
-    # headless drivers and will be silently ignored if passed.
-    #
-    # To use a headless driver, like Poltergeist, update your Gemfile to use
-    # Poltergeist instead of Selenium and then declare the driver name in the
-    # +application_system_test_case.rb+ file. In this case you would leave out the +:using+
-    # option because the driver is headless.
-    #
-    #   require "test_helper"
-    #   require "capybara/poltergeist"
-    #
-    #   class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
-    #     driven_by :poltergeist
-    #   end
-    #
-    # Because <tt>ActionDispatch::SystemTestCase</tt> is a shim between Capybara
-    # and Rails, any driver that is supported by Capybara is supported by system
-    # tests as long as you include the required gems and files.
     include Capybara::DSL
     include SystemTesting::TestHelpers::SetupAndTeardown
     include SystemTesting::TestHelpers::ScreenshotHelper