similar to: rake fails on build server, but not in development

I''m new to ROR, and am working my way through the Agile Web Development Book. In the test application, the authors tell me to test my database connection by performing "rake db:migrate". When I do, I get the error "Don''t know how to build task ''db:migrate''" I''ve been looking around at the files, and I see a reference to a

I''ve upgraded to Rails 1.1.2, and I''m trying to push this change through to our build server (Linux/Oracle) and we are getting some errors in the unit tests using Oracle. Looking at the data in the tests reveals a precision problem. Looking at the tables tells the whole story. My development database contains this table: SQL> describe dls_grids; Name

Hi! Is it possible to run unit tests when no database is configured? Rails recipes mentions putting following piece of code in a file within lib/tasks/ [:test_units,:test_functional,:recent].each do |name| Rake::Task.lookup(name).prerequisites.clear end However this seem to be out-of-date, as task lookup in rake according to RDoc is now done using Rake:Task[name]. But after I updated the

I have just migrated to use Rail 1.1 from 1.0. In the progress of fixing and cleaning up the unit tests. I found the following problem. I am not sure if this is a bug or it is my environment. When I run "rake test_units, some of the index in association tables is not created, this leads to failures for some unit test cases. Thinking that may be because I didn''t setup the

am in a bit of a quandry... I have asked postgresql-users list and haven''t gotten anything to work with... > > How do I change the owner of a schema? > > > > ALTER SCHEMA "public" OWNER to "some_user"; #? > > http://www.postgresql.org/docs/current/interactive/sql-alterschema.html > > The docs explain this very situation. HTML

Is rails + oci8 + mac os x intel a winning combination? It appears that oci8 might be a issue.

I''ve created a model, let''s just call it Person class Person attr_accessor :first_name, :lastname def full_name @first_name + " " + @last_name end end I''m using this in my Rails application. My Rails application does not use a database of any kind, and this model is obviously not a subclass of ActiveRecord::Base. I can''t unit test this

> -----Original Message----- > From: rails-bounces@lists.rubyonrails.org > [mailto:rails-bounces@lists.rubyonrails.org] On Behalf Of Lori Olson > Sent: Tuesday, April 11, 2006 8:04 PM > To: rails@lists.rubyonrails.org > Subject: [Rails] Re: Re: Oracle unit test problem in Rails > 1.1.2/Ruby-OCI 0.1 > > > Wilson Bilkovich wrote: > > On 4/11/06, Lori Olson

Hi all. I am using PostgreSQL in my current project and I have couple of questions on this topic. Previously I have used 3 databases for project. i.e. megaproject_development, megaproject_test and megaproject_development. But I don''t like this variant because of ''rake dump_db_structure'' writes a lot of PostgreSQL specific data for structure file (operators, functions,

Hello All, If I run my unit tests individually using Ruby, they all work correctly. However, if I try to run them using "rake test_units", I get a bunch of error messages. The error messages appear to be caused by rake not loading any of the fixtures into the test database. I am using PostgreSQL on Windows. Does anyone have any suggestions? Many thanks, Bruce. -- Posted via

Can anyone (David?) shed some light on what exactly this warning is complaining about? I started seeing it when I upgraded to Rails 2.1 RC1 and the latest RSpec from git. I''m getting it in some helper specs that I''m writing. And yes, I am including a module there, to reuse some utility methods I originally wrote for my controller tests (I''m switching to specs

After upgrading to Rails 1.1, a lot of my unit tests broke. Turns out when I run rake test_units and it migrates the test database, it adds a not null constraint to every column. I don''t have this specified in my migration, and apparently it works fine with rake migrate if I do ''rake migrate RAILS_ENV=test'', the not null constraints aren''t set. So why when I

I searched thru all the postings about RJS, and I didn''t find one person who complained of problems specific to IE, but that''s what I''ve got. My environment is: Rails 1.0 + RJS Plugin Updated Javascripts to Scriptaculous 1.5.3 (for evalScripts support) Monkeypatched in_place_editor to support evalScripts I have just started using RJS, and I have two .rjs templates.

I recently started using migrations to create the schema of a Rails project I am working on. The database I am using for this project is MySQL. The initial migration creates the table and also includes a number of execute statements (to do some things like setting primary keys, autoincrement on some columns and other messy voodoo). Running "rake migrate" creates the database with no

I''m getting some very weird results when testing my system. If I run my unit tests using => ruby \test\unit\<filename.rb> each of the tests pass. If I run => rake test_units I get several failures, and they all have to deal with the same issue. For instance I''m getting => ActiveRecord::StatementInvalid: RuntimeError: ERROR C42P01 Mrelation

Hello, Can someone explain why my exclude option is not excluding filles as instructed in my script below. I have tried multiple methods and still have been unsuccessful in excluding the one file "test.sql". The methods I have tried are: 1. Removing EXTRAFLAG variable -a 2. Removing using -a 3. Option --include infront of --exclude and behind of --exclude. 4. rsync /software/testdir/

Hi All, In the absence of any clear picture about whether damagecontrol is a practical option for continuous integration, I set up the following scripts on my server to run the rails functional and unit tests each day and mail me the results: :::::::::::::: run_functional_tests.sh :::::::::::::: #!/bin/bash cd /var/www/ruby/srjoseph/prometheus rake test_functional &>

Hello, I am having some trouble running the unit tests for the salted has login generator. I am a bit new to both ruby and rails so I am having a little trouble deciphering the error message I get when running ''rake test_units''. Up till the point where I try to run the unit tests I have followed the quick start guide for the salted hash login generator

Hi Running ''rake test_units'' using the simple example from the intro video is very slow on my computer. While the tests claim to execute in 0.17 secs, the startup time ad 5.3 seconds to the overall job. On the video, these tasks ran in about 1 second. (Maybe David was doing the tests on a dual proc mac or did some video editing, who knows.) But, I don''t think it should

> Matthew Ahrens wrote: > > Ross Newell wrote: > >> What are this issues preventing the root directory being stored on > >> raidz? > >> I''m talking specifically about root, and not boot which I can see > >> would be > >> difficult. > >> > >> Would it be something an amateur programmer could address in a > >>