cafe-grader-web Files · vendor/plugins/rspec_on

cafe-grader-web

Location: cafe-grader-web/vendor/plugins/rspec_on_rails/lib/spec/rails/example.rb

Commit Description:

adjusted partial counter...

Commit Description:

adjusted partial counter git-svn-id: http://theory.cpe.ku.ac.th/grader/web/trunk@279 6386c4cd-e34a-4fa8-8920-d93eb39b512e

References:

r140:4abf143aa577 default

File last commit:

r60:f8c242fd7c91 default

Show/Diff file:

Action:

            
                    vendor/plugins/rspec_on_rails/lib/spec/rails/example.rb
                
             | 47 lines
             | 1.8 KiB
             | text/x-ruby 
             | RubyLexer
             | 
      
            History
        
           Show Full History
         |
          Annotation
         | Raw
         |
              
              Download
              
      dir = File.dirname(__FILE__)

      require 'spec/rails/example/ivar_proxy'

      require 'spec/rails/example/assigns_hash_proxy'

      require "spec/rails/example/render_observer"

      require "spec/rails/example/rails_example_group"

      require "spec/rails/example/model_example_group"

      require "spec/rails/example/functional_example_group"

      require "spec/rails/example/controller_example_group"

      require "spec/rails/example/helper_example_group"

      require "spec/rails/example/view_example_group"

      module Spec

        module Rails

          # Spec::Rails::Example extends Spec::Example (RSpec's core Example module) to provide

          # Rails-specific contexts for describing Rails Models, Views, Controllers and Helpers.

          #

          # == Model Examples

          #

          # These are the equivalent of unit tests in Rails' built in testing. Ironically (for the traditional TDD'er) these are the only specs that we feel should actually interact with the database.

          #

          # See Spec::Rails::Example::ModelExampleGroup

          #

          # == Controller Examples

          #

          # These align somewhat with functional tests in rails, except that they do not actually render views (though you can force rendering of views if you prefer). Instead of setting expectations about what goes on a page, you set expectations about what templates get rendered.

          #

          # See Spec::Rails::Example::ControllerExampleGroup

          #

          # == View Examples

          #

          # This is the other half of Rails functional testing. View specs allow you to set up assigns and render

          # a template. By assigning mock model data, you can specify view behaviour with no dependency on a database

          # or your real models.

          #

          # See Spec::Rails::Example::ViewExampleGroup

          #

          # == Helper Examples

          #

          # These let you specify directly methods that live in your helpers.

          #

          # See Spec::Rails::Example::HelperExampleGroup

          module Example

          end

        end

      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

				dir = File.dirname(__FILE__)

				require 'spec/rails/example/ivar_proxy'
				require 'spec/rails/example/assigns_hash_proxy'

				require "spec/rails/example/render_observer"
				require "spec/rails/example/rails_example_group"
				require "spec/rails/example/model_example_group"
				require "spec/rails/example/functional_example_group"
				require "spec/rails/example/controller_example_group"
				require "spec/rails/example/helper_example_group"
				require "spec/rails/example/view_example_group"

				module Spec
				module Rails
				# Spec::Rails::Example extends Spec::Example (RSpec's core Example module) to provide
				# Rails-specific contexts for describing Rails Models, Views, Controllers and Helpers.
				#
				# == Model Examples
				#
				# These are the equivalent of unit tests in Rails' built in testing. Ironically (for the traditional TDD'er) these are the only specs that we feel should actually interact with the database.
				#
				# See Spec::Rails::Example::ModelExampleGroup
				#
				# == Controller Examples
				#
				# These align somewhat with functional tests in rails, except that they do not actually render views (though you can force rendering of views if you prefer). Instead of setting expectations about what goes on a page, you set expectations about what templates get rendered.
				#
				# See Spec::Rails::Example::ControllerExampleGroup
				#
				# == View Examples
				#
				# This is the other half of Rails functional testing. View specs allow you to set up assigns and render
				# a template. By assigning mock model data, you can specify view behaviour with no dependency on a database
				# or your real models.
				#
				# See Spec::Rails::Example::ViewExampleGroup
				#
				# == Helper Examples
				#
				# These let you specify directly methods that live in your helpers.
				#
				# See Spec::Rails::Example::HelperExampleGroup
				module Example
				end
				end
				end