specjour 0.2.4 → 0.2.5

data/History.markdown

@@ -1,5 +1,11 @@
 History
 =======
+0.2.5
+-----
+*2010-05-13*
+
+* [changed] The rails plugin now runs in a Rails.configuration.after_intialize
+  block
 
 0.2.4
 -----

data/README.markdown

@@ -37,7 +37,7 @@ Run the rake task to distribute the features among the managers you started.
     $ rake specjour:cucumber
 
 ## Rails
-Each worker should run their specs in an isolated database. Modify the test database name in your `config/database.yml` to include the following environment variable (Influenced by [parallel_tests](http://github.com/grosser/parallel_tests)):
+Each worker should run their specs in an isolated database. Modify the test database name in your `config/database.yml` to include the following environment variable (Influenced by [parallel\_tests](http://github.com/grosser/parallel_tests)):
 
     test:
       database: blog_test<%=ENV['TEST_ENV_NUMBER']%>
@@ -49,7 +49,7 @@ Add the specjour gem to your project:
 Doing this enables a rails plugin wherein each worker will attempt to clear its database tables before running any specs via `DELETE FROM <table_name>;`. Additionally, test databases will be created if they don't exist (i.e. `CREATE DATABASE blog_test8` for the 8th worker) and your schema will be loaded when the database is out of date.
 
 ### Customizing database setup
-If the plugin doesn't set up the database properly for your test suite, bypass it entirely. Remove specjour as a project gem and create your own initializer to setup the database. Specjour sets the environment variable PREPARE_DB when it runs your specs so you can look for that when setting up the database.
+If the plugin doesn't set up the database properly for your test suite, bypass it entirely. Remove specjour as a project gem and create your own initializer to setup the database. Specjour sets the environment variable PREPARE\_DB when it runs your specs so you can look for that when setting up the database.
 
     # config/initializers/specjour.rb
 
@@ -85,7 +85,7 @@ Distributed testing doesn't have to happen over multiple machines, just multiple
 * voxdolo - Endless support, alpha testing, various patches
 * leshill - Made rsync daemon configurable
 * testjour - Ripped off your name
-* parallel_tests - Made my test suite twice as fast
+* parallel\_tests - Made my test suite twice as fast
 
 ## Note on Patches/Pull Requests
 
@@ -101,4 +101,4 @@ Distributed testing doesn't have to happen over multiple machines, just multiple
 
 ## Copyright
 
-Copyright (c) 2010 Sandro Turriate. See MIT_LICENSE for details.
+Copyright (c) 2010 Sandro Turriate. See MIT\_LICENSE for details.

data/VERSION

@@ -1 +1 @@
-0.2.4
+0.2.5

data/lib/specjour.rb

@@ -23,7 +23,7 @@ module Specjour
   autoload :Cucumber, 'specjour/cucumber'
   autoload :Rspec, 'specjour/rspec'
 
-  VERSION = "0.2.4".freeze
+  VERSION = "0.2.5".freeze
 
   class Error < StandardError; end
 

data/rails/init.rb

@@ -1,4 +1,6 @@
 if ENV['PREPARE_DB']
-  require 'specjour/db_scrub'
-  Specjour::DbScrub.scrub
+  Rails.configuration.after_initialize do
+    require 'specjour/db_scrub'
+    Specjour::DbScrub.scrub
+  end
 end

data/specjour.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{specjour}
-  s.version = "0.2.4"
+  s.version = "0.2.5"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Sandro Turriate"]
-  s.date = %q{2010-05-10}
+  s.date = %q{2010-05-13}
   s.default_executable = %q{specjour}
   s.description = %q{Distribute your spec suite amongst your LAN via Bonjour.}
   s.email = %q{sandro.turriate@gmail.com}

metadata

@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
   segments: 
   - 0
   - 2
-  - 4
-  version: 0.2.4
+  - 5
+  version: 0.2.5
 platform: ruby
 authors: 
 - Sandro Turriate
@@ -14,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-05-10 00:00:00 -04:00
+date: 2010-05-13 00:00:00 -04:00
 default_executable: specjour
 dependencies: 
 - !ruby/object:Gem::Dependency