1
0
Fork 0
mirror of https://github.com/thoughtbot/shoulda-matchers.git synced 2022-11-09 12:01:38 -05:00
thoughtbot--shoulda-matchers/test
Ryan McGeary f517592c45 Fix for pluralization problem in should_belong_to [#19] [Earle Clubb, Anthony Caliendo]
should_belong_to :address  # => now works as expected
2008-08-08 19:04:27 -04:00
..
fixtures Enhanced assert_good/bad_value assertions in preparation for stateful AR validations 2008-07-31 00:04:05 -04:00
functional Change should_assign_to and should_not_assign_to to allow multiple names (#22) 2008-07-31 11:26:27 -04:00
other Enhanced assert_good/bad_value assertions in preparation for stateful AR validations 2008-07-31 00:04:05 -04:00
rails_root Fix for pluralization problem in should_belong_to [#19] [Earle Clubb, Anthony Caliendo] 2008-08-08 19:04:27 -04:00
unit Fix for pluralization problem in should_belong_to [#19] [Earle Clubb, Anthony Caliendo] 2008-08-08 19:04:27 -04:00
README Rid the symlink behavior under test/rails_root/vendor/plugins 2008-07-11 21:03:50 -04:00
test_helper.rb Rid the symlink behavior under test/rails_root/vendor/plugins 2008-07-11 21:03:50 -04:00

The Shoulda test suite (in particular - the tests that test shoulda)

Quick overview:

The test directory contains the following files and subdirectories:

* rails_root - contains the stripped down rails application that the tests run against.  The rails root contains:
** the models, controllers, and views defined under app/
** the sqlite3.rb environment file
** a migration file for each model
** a shoulda initializer that simulates loading the plugin but without relying on vendor/plugins
* fixtures - contain the sample DB data for each model
* functional - controller tests for each of the controllers under rails_root/app
* unit - model tests for each of the models under rails_root/app
* other - tests for the shoulda contexts, should statements, and assertions
* test_helper.rb - responsible for initializing the test environment
** sets the rails_env to sqlite3
** sets the rails_root
** runs all the migrations against the in-memory sqlite3 db
** adds some magic to load the right fixture files

In order to add a new model (or controller) to the test suite:

* add that model to rails_root/app/models
* add a migration for that model
* add a fixture file
* add a test for that file under test/units

Dependencies:

* Rails gem installed in the host system
* A working sqlite3 installation.

If you have problems running these tests, please notify the mailing list:  shoulda@googlegroups.com

- Tammer Saleh <tsaleh@thoughtbot.com>