This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 13ff067422765a5e113da6e0188b4fc9ca9dccfb
tree dcd1b142d005d186332fb0d5f4015cce49475f9d
parent f062a6924e4b4539eef1eb2d318f2b82367e692f
tree dcd1b142d005d186332fb0d5f4015cce49475f9d
parent f062a6924e4b4539eef1eb2d318f2b82367e692f
shoulda / test
| name | age | message | |
|---|---|---|---|
| .. | |||
| |
README | Mon Jan 19 08:29:54 -0800 2009 | |
| |
fail_macros.rb | Tue Jun 02 19:41:17 -0700 2009 | |
| |
fixtures/ | Sun Aug 31 09:14:16 -0700 2008 | |
| |
functional/ | Thu May 07 20:43:47 -0700 2009 | |
| |
matchers/ | ||
| |
model_builder.rb | Tue May 05 18:39:22 -0700 2009 | |
| |
other/ | ||
| |
rails_root/ | ||
| |
rspec_test.rb | Tue May 05 18:39:22 -0700 2009 | |
| |
test_helper.rb | Tue May 05 18:39:22 -0700 2009 | |
| |
unit/ |
test/README
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 test.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 test ** 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>








