similar to: test:prepare failure with enum columns

I have spent sometime this afternoon learning how to unit test rails applications and integrate the Cerberus CI tool. One key area confuses me however, and I would appreciate other peoples views of how best to overcome the issue. My understanding is that the ''test'' and ''test:units'' have the db:test:prepare pre-requisite which copies the schema from dev to the

hello all, i have a problem with test_truth. require ''test_helper'' class MyDataTest < ActiveSupport::TestCase def test_truth assert true end end this should ok without failures or errors. but it failure: 1) Error: test_truth(MyDataTest): ActiveRecord::StatementInvalid: Mysql::Error: Table ''alldataserver_test.members'' doesn''t exist: DELETE

This is what I have inside a rake task. In this rake task I need to call another rake task called email:send_messages. However I need to pass the RAILS_ENV as ''staging''. Rake::Task["rake:email:send_messages"].invoke I tried a lot of variations but none of them work. Rake::Task["rake:email:send_messages"].invoke RAILS_ENV=staging

On the wiki it says to migrate your DB to production, you can run: rake migrate RAILS_ENV="production" This is taken from: http://wiki.rubyonrails.com/rails/pages/UnderstandingMigrations My database is set up with correct MySQL permissions granted and the database.yml is pointing at it. I get no errors when I run it, but equally my production database does not change at all.

Hello! I''m trying to install puppet dashboard according to the instructions in the documentation : http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html I am installing it from the .deb package, however after installation I cannot find the "settings.yml" file. Also, when trying to "prepare schema" by running rake RAILS_ENV=production db:migrate it

All, I have two migration files, file 1 and file 2. For reasons that I don''t want to go into unless I must, I want to only run file 2 on my production database (file 1 contains a bunch of table creation stuff for already existing tables). I figured if I created a schema_info table and set the version in it to 1, then I could just run rake db:migrate RAILS_ENV=production and just

In development and production, I''ve got postgresql constraints that prevent deleting a CaseManager if there is a Client that belongs to that CaseManager. In unit tests...and obviously in my testing db, those restrictions don''t get added. Is it wrong to test for deleting dependent records in unit tests? Craig --~--~---------~--~----~------------~-------~--~----~ You received

All, Just read in the Capistrano manual about the Capistrano "migrate" task. There it says that: "By default, all this task does is change to the directory of your current release (as indicated by the current symlink), and run rake RAILS_ENV=production migrate. You can specify that it should run against the latest release (regardless of what the current release is) by setting

I''m deploying new rails applications. Everything works well except when it comes to the db migration: * executing "cd /var/rails/benefits_test/releases/20101129190121 && /opt/ruby-enterprise-1.8.7-2010.02/bin/rake RAILS_ENV=production db:util:migrate" servers: ["ps-test-app1"] [ps-test-app1] executing command ** [out :: ps-test-app1] (in

Hi guys. I''m writing a plugin for use in the test environment. However, when I run ``rake test'''' or ``rake spec'''', RAILS_ENV is set to "development" when my plugin''s init.rb is run. How do you configure a plugin to load require a file in the test environment? Thanks, Nick --~--~---------~--~----~------------~-------~--~----~ You

When I run ''rake remote:migrate'' teh task fails with the error: ''uninitialized constant Enum'' Other rake remote tasks including rake deploy, update_code etc all work fine. I get the same error whether I run ''rake remote:migrate'' from my local machine or when i run ''rake RAILS_ENV=production migrate'' in the root of my

Railsters: Despite Rails being the only Web platform designed for TDD, a lot of its test infrastructure is still "cargo cult" - imitating other test rigs instead of understanding their principles. Most importantly, tests should run instantly. There''s no excuse for breaking this rule, and if you invent a platform that can''t obey it then you are doing something

I''m having some issues running rake commands for puppet dashboard. Here is one of the symptoms (see below). I''m a little new to setting up rails/rack applications, so I may be making a common mistake. It looks like gems are already packaged with dashboard, specifically rack-1.01. Should that gem just work out of the box? Command: rake RAILS_ENV=production reports:prune upto=1

no matter what I try I keep getting this error: rake RAILS_ENV=production db:migrate --trace ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate rake aborted! Access denied for user ''dashboard''@''localhost'' to database ''production'' I have setup the dashboard user in mysql DB, tested

Just released a new version of the _Managed Fixtures_ plugin, previously known as _Export Fixtures_. The name change comes with some added functionality for managing the fixtures, primarily with two new import tasks for importing specific Models or all of them within the test/fixtures directory. Both new import tasks take the exported fixtures, and allow you to directly import one, or all of

Hello, I try config puppet with foreman frontend. Into puppetmasterd I create modules "test" and create init.pp: # Create "/tmp/testfile" if it doesn''t exist. class test_class { file { "/tmp/testfile": ensure => present, mode => 644, owner => root, group => root } } Configure nodes in site.pp and import

Hi, I need fix any bugs in a rails project. The problem is every time I change anything in javascript I have to make bundle exec rake rails_group=assets assets:clean RAILS_ENV=development and then bundle exec rake rails_group=assets assets:precompile RAILS_ENV=development and finaly restart the rails server. This way spend 10 min. Exists any other solution? -- You received this message

I''m going through the ''Depot'' project in "Agile Web Development with Rails". I just made the 003_add_test_data.rb file and when I do a "rake db:migrate", I get this error and I can''t figure out what is wrong: rake aborted! ./db/migrate//003_add_test_data.rb:5: parse error, unexpected tSYMBEG 5. :description => (and the

Hi Everybody, I''m playing around with the engines created by James Adam and I bumped into the following. I would like the rake bootstrap command to use the testing database and I just know there''s an easy way to do so. I could have just copied the dev db''s to the test db''s but I think I''m missing something fundamental here. Hints are very welcome.

Dear all, I am setting some constants in an initializer, which are used in validations in my models. When I run RAILS_ENV=test rake gems:install I get missing constant errors for these, but not when I run RAILS_ENV=development rake gems:install It only happens for the gems:install task in test. Everything else (e.g. rake test) works as expected. What could be the problem? Thanks for your