Updating running tests instructions.

Author: metaskills

Gemfile

@@ -2,11 +2,18 @@
 source :rubygems
 
 gemspec :path => ENV['RAILS_SOURCE']
-gem 'arel', :path => ENV['AREL'] if ENV['AREL']
-gem 'tiny_tds', :path => ENV['TINYTDS_SOURCE'] if ENV['TINYTDS_SOURCE']
+gem 'arel', :path => ENV['AREL']
+
+group :tinytds do
+  if ENV['TINYTDS_SOURCE']
+    gem 'tiny_tds', :path => ENV['TINYTDS_SOURCE']
+  else
+    gem 'tiny_tds'
+  end
+end
 
 group :odbc do
-  gem 'ruby-odbc', '0.99992'
+  gem 'ruby-odbc'
 end
 
 group :development do

RUNNING_UNIT_TESTS

@@ -20,22 +20,49 @@ Clone adapter git://github.com/rails-sqlserver/activerecord-sqlserver-adapter.gi
 The master branch is the one under development for rails 3, track the repos 2-3-stable 
 branch for 2.x development.
 
-The tests of this adapter depend on the existence of the rails source which can 
-be cloned at git://github.com/rails/rails.git. Like the adapter, the master is 
-for 3.x development and it has its own 2-x-stable branches which can be tracked 
-or checked out for local testing.
+The tests of this adapter depend on the existence of the rails and/or arel source 
+which can be cloned at git://github.com/rails/rails.git and git://github.com/rails/arel.git
 
-Set the RAILS_SOURCE environment variable with the full path of the rails repo. 
-It is optional, but you can set an AREL environment variable to the path of your 
-clone of the official git fork of arel found at git://github.com/rails/arel.git. 
-As of now there is no need to do this as our Gemfile will source this and we currently 
-host our own compiler in this project. 
+Once you have cloned these repos set the RAILS_SOURCE and AREL environment variables
+to their full path. For instance:
+
+  ∴ echo $RAILS_SOURCE
+  /Users/kencollins/Repositories/rails
+  
+  ∴ echo $AREL
+  /Users/kencollins/Repositories/arel
+
+Do not forget to checkout the version tags of each repo that match either our gemspec 
+or what version your tests target. For instance, v3.0.3 tag for ActiveRecord and 
+v2.0.7 for ARel. 
+
+
+= Setup Connection Mode
+
+The Gemfile contains groups for :tinytds and :odbc. By default it will install both gems 
+which allows you to run the full test suite in either connection mode. If for some reason 
+any one of these is problematic or of no concern, you could always for go the bundling 
+of those gems with something like this.
+
+  ∴ bundle install --without odbc
+
+
+= Finally
 
 Now with all that out of the way you can run "bundle install" to hook everything up. 
 Our tests use bundler to setup the load paths correctly. If all goes well, you should 
-be able to run "rake test" which will load all the adapter tests followed by the 
+be able to run "rake test:dblib" which will load all the adapter tests followed by the 
 core ActiveRecord tests. Lastly, it is typically good practice to do your work 
 on a local branch of our remote tracking branch.
 
 
+= Current Expected Failures
+
+* test_count_explicit_columns(RelationTest) <0> expected but was <7>
+  I believe this failure is actually incorrect for other DBs to be passing and 
+  will explore a patch to rails which disables ambiguous results sets.
+
+* Misc Date/Time object instance matches when using ODBC mode.
+
+