cafe-grader-web Files · test/test

cafe-grader-web

Location: cafe-grader-web/test/test_helper.rb

Commit Description:

shows problem descriptions on first page

Commit Description:

shows problem descriptions on first page

References:

r215:776188eca107 default

File last commit:

r0:adb458d2f524 default

Show/Diff file:

Action:

            
                    test/test_helper.rb
                
             | 28 lines
             | 1.3 KiB
             | text/x-ruby 
             | RubyLexer
             | 
      
            History
        
           Show Full History
         |
          Annotation
         | Raw
         |
              
              Download
              
      ENV["RAILS_ENV"] = "test"

      require File.expand_path(File.dirname(__FILE__) + "/../config/environment")

      require 'test_help'

      class Test::Unit::TestCase

        # Transactional fixtures accelerate your tests by wrapping each test method

        # in a transaction that's rolled back on completion.  This ensures that the

        # test database remains unchanged so your fixtures don't have to be reloaded

        # between every test method.  Fewer database queries means faster tests.

        #

        # Read Mike Clark's excellent walkthrough at

        #   http://clarkware.com/cgi/blosxom/2005/10/24#Rails10FastTesting

        #

        # Every Active Record database supports transactions except MyISAM tables

        # in MySQL.  Turn off transactional fixtures in this case; however, if you

        # don't care one way or the other, switching from MyISAM to InnoDB tables

        # is recommended.

        self.use_transactional_fixtures = true

        # Instantiated fixtures are slow, but give you @david where otherwise you

        # would need people(:david).  If you don't want to migrate your existing

        # test cases which use the @david style and don't mind the speed hit (each

        # instantiated fixtures translates to a database query per test method),

        # then set this back to true.

        self.use_instantiated_fixtures  = false

        # Add more helper methods to be used by all tests here...

      end

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository permissions settings

Sign in to your account

Last Author

				ENV["RAILS_ENV"] = "test"
				require File.expand_path(File.dirname(__FILE__) + "/../config/environment")
				require 'test_help'

				class Test::Unit::TestCase
				# Transactional fixtures accelerate your tests by wrapping each test method
				# in a transaction that's rolled back on completion. This ensures that the
				# test database remains unchanged so your fixtures don't have to be reloaded
				# between every test method. Fewer database queries means faster tests.
				#
				# Read Mike Clark's excellent walkthrough at
				# http://clarkware.com/cgi/blosxom/2005/10/24#Rails10FastTesting
				#
				# Every Active Record database supports transactions except MyISAM tables
				# in MySQL. Turn off transactional fixtures in this case; however, if you
				# don't care one way or the other, switching from MyISAM to InnoDB tables
				# is recommended.
				self.use_transactional_fixtures = true

				# Instantiated fixtures are slow, but give you @david where otherwise you
				# would need people(:david). If you don't want to migrate your existing
				# test cases which use the @david style and don't mind the speed hit (each
				# instantiated fixtures translates to a database query per test method),
				# then set this back to true.
				self.use_instantiated_fixtures = false

				# Add more helper methods to be used by all tests here...
				end