thr3ads.net - Rails - rake test without running re-creating database? [Jun 2007]

If this information is useful, please help other people find it:
Share via:

Mark

2007-Jun-27 13:39 UTC

rake test without running re-creating database?

Hi,

Complexly new to rails testing and having a few problems.

Please correct me if I have any of this wrong:
When I run rake test this first re-cerate''s my test database, however
because I am using a data type that is unsupported by rails, rake is
aborted.

Is there a way to run the tests without recreating the database?

Thanks
Mark

-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Ferdouse Ara

2007-Jun-27 15:02 UTC

head link

Re: rake test without running re-creating database?

Hi,

Please can you help me with the following:

Looking for a Ruby on Rails Developer, Salary £30K-£60K, Leicester, City 
Centre

Use the latest web technology Ruby on Rails.
To develop professional web applications.
Must have written previous Rail applications.
Need the talents of a smart, experienced programmer.
Need to be attentive to detail, a team-player and responsible.
Require previous commercial experience with Ruby on Rails and dealing 
with Database Schema''s to Front End Applications.

Involved with creative projects which are making them a big name in the 
gaming and video industries (sony and microsoft).

Would you be interested or do you know anyone who would be interested as 
there are several positions available.

I appreciate your help in this.

Ferdouse Ara
Technical Recruitment Consultant

Precision Recruitment UK Ltd
Tel +44 (0) 116 2545488
Fax +44 (0) 871 2778928
http://www.precisionrecruitment.co.uk



-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Arsen7

2007-Jun-29 10:27 UTC

head link

Re: rake test without running re-creating database?

Mark napisał(a):> Hi,
>
> Complexly new to rails testing and having a few problems.
>
> Please correct me if I have any of this wrong:
> When I run rake test this first re-cerate''s my test database,
however
> because I am using a data type that is unsupported by rails, rake is
> aborted.
>
> Is there a way to run the tests without recreating the database?
Better solution would be to change schema format to ''sql'' in
config/
environment.rb:

  config.active_record.schema_format = :sql

then the database-native-dump will be used to recreate the test
database.

Of course, you can make rake to not recreate the database, but I don''t
remember how. ;-)
Look for the rake tasks sources in
/usr/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake and
databases.rake
(change version numbers when necessary).


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Jean Nibee

2007-Jun-29 12:46 UTC

head link

Re: rake test without running re-creating database?

Arsen7 wrote:> 
> Better solution would be to change schema format to ''sql''
in config/
> environment.rb:
> 
>   config.active_record.schema_format = :sql
> 
> then the database-native-dump will be used to recreate the test
> database.
> 
> Of course, you can make rake to not recreate the database, but I
don''t
> remember how. ;-)
> Look for the rake tasks sources in
> /usr/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake and
> databases.rake
> (change version numbers when necessary).
I would be more concerned that you can''t create that special data type 
then ''hacking'' the way Rake handles the DB migrations.

Just use a string for the database specific sql you want used in place 
of the symbols on the method you''re executing in your migration.

My Migration shows example with ''tinyint'', which is not a
valid symbol
(data type) in Rails.
>>>>>>>>>> migrationcreate_table :testing do |t|
  t.column :last_updated, :timestamp, :null => false
  t.column :info, ''tinyint(2) not null'', :default => 0
end


jbateman@the-necropolis:~/sandbox/shinny/trunk$ rake db:migrate
(in /home/jbateman/sandbox/shinny/trunk)
Using AdapterExtensions
== CreateTesting: migrating 
==================================================-- create_table(:testing)
   -> 0.1637s
== CreateTesting: migrated (0.1640s) 
=========================================<<<<<<<<<<
end rake


mysql> desc testing;
+--------------+------------+------+-----+---------+----------------+
| Field        | Type       | Null | Key | Default | Extra          |
+--------------+------------+------+-----+---------+----------------+
| id           | int(11)    | NO   | PRI | NULL    | auto_increment | 
| last_updated | datetime   | NO   |     |         |                | 
| info         | tinyint(2) | NO   |     | 0       |                | 
+--------------+------------+------+-----+---------+----------------+

-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Arsen7

2007-Jun-29 14:30 UTC

head link

Re: rake test without running re-creating database?

Jean Nibee wrote:> My Migration shows example with ''tinyint'', which is not a
valid symbol
> (data type) in Rails.
>
> >>>>>>>>>> migration
> create_table :testing do |t|
>   t.column :last_updated, :timestamp, :null => false
>   t.column :info, ''tinyint(2) not null'', :default => 0
> end
[...]> mysql> desc testing;
> +--------------+------------+------+-----+---------+----------------+
> | Field        | Type       | Null | Key | Default | Extra          |
> +--------------+------------+------+-----+---------+----------------+
> | id           | int(11)    | NO   | PRI | NULL    | auto_increment |
> | last_updated | datetime   | NO   |     |         |                |
> | info         | tinyint(2) | NO   |     | 0       |                |
> +--------------+------------+------+-----+---------+----------------+
AFAIK test-database recreation does not use migrations, but database
dump, so if you use database-specific types or constructs (triggers,
for example) you should use :sql dump type, as the default tries to
express the database structure using rails syntax. You can look in
the ./db/ directory and examine files found there (after `rake test`)
to see how the dump looks like.
What is the ''desc testing'' output if you do it in the test
database
after rake db:test:prepare ?

By the way, currently ''create_table t.column'' allows
database-native
types, but there are problems when you use it in ''add_column''.
I saw
it fixed in SVN, though.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Michael Latta

2007-Jun-29 15:36 UTC

head link

Re: rake test without running re-creating database?

I found a post (http://snippets.dzone.com/posts/show/2031) about how  
to make tests use migrations rather than dumping the dev database.  I  
find this has more integrity as that is how a real production  
environment would be created.  It also tests the migrations which is  
a good thing.  I can imagine also having tests that migrate to a  
specific point then create data, then migrate further to test updates  
of the schema.

Here is the code from that post which I put at the end of my rake file:


module Rake
   module TaskManager
     def redefine_task(task_class, args, &block)
       task_name, deps = resolve_args(args)
       task_name = task_class.scope_name(@scope, task_name)
       deps = [deps] unless deps.respond_to?(:to_ary)
       deps = deps.collect {|d| d.to_s }
       task = @tasks[task_name.to_s] = task_class.new(task_name, self)
       task.application = self
       task.add_comment(@last_comment)
       @last_comment = nil
       task.enhance(deps, &block)
       task
     end
   end
   class Task
     class << self
       def redefine_task(args, &block)
         Rake.application.redefine_task(self, args, &block)
       end
     end
   end
end

def redefine_task(args, &block)
   Rake::Task.redefine_task(args, &block)
end
namespace :db do
   namespace :test do

     desc ''Prepare the test database and migrate schema''
     redefine_task :prepare => :environment do
       if defined?(ActiveRecord::Base) && ! 
ActiveRecord::Base.configurations.blank?
         #Rake::Task[{ :sql  => "db:test:clone_structure", :ruby
=>
"db:test:clone", :migration => "db:test:migrate" } 
[ActiveRecord::Base.schema_format]].invoke
         Rake::Task["db:test:migrate"].invoke
       end
     end

     desc ''Use the migrations to create the test database''
     task :migrate => ''db:test:purge'' do
       begin
         ActiveRecord::Base.establish_connection 
(ActiveRecord::Base.configurations[''development''])
         schema_version = ActiveRecord::Base.count_by_sql("SELECT  
version AS count_all FROM schema_info LIMIT 1;")
         ActiveRecord::Base.establish_connection 
(ActiveRecord::Base.configurations[''test''])
         ActiveRecord::Migrator.migrate("db/migrate/", schema_version)
       rescue
         puts "The development database doesn''t exist or no  
migrations have been run on it."
       end
     end

   end
end




Michael




On Jun 29, 2007, at 7:30 AM, Arsen7 wrote:
>
>
> Jean Nibee wrote:
>> My Migration shows example with ''tinyint'', which is
not a valid
>> symbol
>> (data type) in Rails.
>>
>>>>>>>>>>>> migration
>> create_table :testing do |t|
>>   t.column :last_updated, :timestamp, :null => false
>>   t.column :info, ''tinyint(2) not null'', :default
=> 0
>> end
> [...]
>> mysql> desc testing;
>> +--------------+------------+------+-----+---------+----------------+
>> | Field        | Type       | Null | Key | Default | Extra          |
>> +--------------+------------+------+-----+---------+----------------+
>> | id           | int(11)    | NO   | PRI | NULL    | auto_increment |
>> | last_updated | datetime   | NO   |     |         |                |
>> | info         | tinyint(2) | NO   |     | 0       |                |
>> +--------------+------------+------+-----+---------+----------------+
>
> AFAIK test-database recreation does not use migrations, but database
> dump, so if you use database-specific types or constructs (triggers,
> for example) you should use :sql dump type, as the default tries to
> express the database structure using rails syntax. You can look in
> the ./db/ directory and examine files found there (after `rake test`)
> to see how the dump looks like.
> What is the ''desc testing'' output if you do it in the
test database
> after rake db:test:prepare ?
>
> By the way, currently ''create_table t.column'' allows
database-native
> types, but there are problems when you use it in
''add_column''. I saw
> it fixed in SVN, though.
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google  
> Groups "Ruby on Rails: Talk" group.
> To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> To unsubscribe from this group, send email to rubyonrails-talk- 
> unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> For more options, visit this group at http://groups.google.com/ 
> group/rubyonrails-talk?hl=en
> -~----------~----~----~----~------~----~------~--~---
>

Phlip

2007-Jun-30 21:52 UTC

head link

Re: rake test without running re-creating database?

Mark wrote:
> Please correct me if I have any of this wrong:
> When I run rake test this first re-cerate''s my test database,
however
> because I am using a data type that is unsupported by rails, rake is
> aborted.
Where are you using this data type?

I don''t know if a non-primitive data type will interact correctly
inside a
fixture, but you should at least be able to put this in the top of your 
fixture:

<% require ''my_esoteric_type'' %>

fix1:
    id: 2
    data: etc.
> Is there a way to run the tests without recreating the database?
Yes. Use rake test --trace --dry-run, find the name of the low-level task 
that calls the actual tests, and invoke that on a command line instead of 
test.

Tip: You want to use fixtures in your tests. You need them now, and you need 
them later. Trust me! Work a little, now, to fix them with this data type.

-- 
  Phlip
  http://www.oreilly.com/catalog/9780596510657/
  "Test Driven Ajax (on Rails)"
  assert_xpath, assert_javascript, & assert_ajax 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Mark

2007-Jul-02 15:47 UTC

head link

Re: rake test without running re-creating database?

Thanks all

adding this to the config did the job!
config.active_record.schema_format = :sql

-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Rails - Jun 2007 - rake test without running re-creating database?

rake test without running re-creating database?

Re: rake test without running re-creating database?

Re: rake test without running re-creating database?

Re: rake test without running re-creating database?

Re: rake test without running re-creating database?

Re: rake test without running re-creating database?

Re: rake test without running re-creating database?

Re: rake test without running re-creating database?