similar to: use_transactional_fixtures= and Test::Rails

Folks, I checked my test_helper.rb and it has self.use_transactional_fixtures = true My code was generated with 1.1.2 and I''m using 1.1.3 right now after but the error persists. I googled for this issue and it appears that a require is missing or something like that. I can''t figure it out, please help! /opt/local/bin/ruby -Ilib:test

I upgraded a working app from rails 2.1 to 2.3.2. Now when I run rake test:units I get this error: /usr/lib/ruby/gems/1.8/gems/ activesupport-2.3.2/lib/active_support/test_case.rb:17: superclass mismatch for class TestCase (TypeError) I generated a new test app and all tests run OK. For the upgrade I ran rake:update and renamed the class in test_helper to ActiveSupport::TestCase. Also renamed

Greetings: I am using Sqlite3 database with my Rails app. When I try and run "rake tests" for the app it always fails with the error: ** Invoke default (first_time) ** Invoke test (first_time) ** Execute test ** Invoke test:units (first_time) ** Invoke db:test:prepare (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:test:prepare ** Invoke

I recently upgraded to Rails 1.0 and started a new project. I''ve started writing some tests, but when I run rake, I just get the following... Amnesia:~/Development/Rails/pog shad$ rake (in /Users/shad/Development/Rails/pog) /usr/bin/ruby -Ilib:test "/usr/lib/ruby/gems/1.8/gems/rake-0.6.2/lib/rake/rake_test_loader.rb" "test/unit/pog_test.rb"

I have three files organization.rb, company.rb, and department.rb. I want to ensure the department always has a company require File.dirname(__FILE__) + ''/../test_helper'' class OrganizationTest < Test::Unit::TestCase fixtures :organizations def setup @smo = organizations(:smo) end def test_department_company_defaults_to_parent org = Department.new(:name =>

Googling around, I found that apparently adding to the gem file will fix my problems, but where do i find the gem file? what is the name of the gem file? "group :test do # Pretty printed test output gem ''minitest'' ####### add this line ####### end" Here is what happens when i run rake test, please note that i have already installed minitest

I am trying to get a local installation of OpenStreetView, on Ubuntu 10.10 On installing Rails (2.3.8) and OSV code using git, when I issue "rake" command, I get response, which is reproduced below signature. What is missing from my installation? -- .O.C. $ rake (in /home/meet/OSV/OpenStreetView) /usr/bin/ruby1.8 -I"lib:test" "/var/lib/gems/1.8/gems/rake-0.8.7/lib/

rails -v=2.3.8 gem -v= 1.4.2 ruby -v=1.8.7 When i issue the "rake" command ,it gives the following error . (in /home/amrit/amrit/OSV/OpenStreetView) /usr/bin/ruby1.8 -I"lib:test" "/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb" "test/functional/main_controller_test.rb" "test/functional/upload_controller_test.rb"

If you see this error message: undefined method `use_transactional_fixtures='' for Test::Unit::TestCase:Class (NoMethodError) You should check all your dependencies, all the lines containing require and especially require_dependency. You have probably done a refactoring "Rename" a class and forgot to propagate the change everywhere! More details on

Hi! I would really like to find a way to allow me to write RSpec specifications for code that use database transactions. I know I can set config.use_transactional_fixtures = false in my spec_helper.rb. That works, and that''s great, but it will (I think) slow down my specs quite a bit. I would like to turn off transactional fixtures for just a single spec (describe), or even

I left ":memory:" in database.yml for testing and the most simple tests in the Agile book do not work (see trace below for test_truth). Since that''s what comes with the distributed database.yml I suppose it''s me doing something wrong. Did someone get SQLite ":memory:" working? How does it grab the schema? -- fxn % rake test_units (in

Hi all, This testing problem has been a sink for time today, and is still unresolved. Basically I have some unit tests that test simple functions (example below) that depend on join operations in a habtm relationship, and I suspect I am getting "false" failures, i.e ones that do not logically make any sense. I need fresh sets of eyes to take a look and see if I''m mising

All, I''ve been trying to figure out a strange bug in one of my applications that I think I''ve narrowed down to a problem with rails fixtures. It seems as though the after_create callback is being run twice when I save a record. This is only happening a) in the test environment, and b) when there is a fixture file for that table. The test below only prints "Doing

Hi all, I just hit a big wall involving a legacy database. I''ve got an active record class called "School" that uses "set_table_name ''old_school''" to map to a legacy database table: class School < ActiveRecord::Base set_table_name ''old_school'' end It works great, until I''m testing and I want to use fixtures.

Hi all, I just hit a big wall involving a legacy database. I''ve got an active record class called "School" that uses "set_table_name ''old_school''" to map to a legacy database table: class School < ActiveRecord::Base set_table_name ''old_school'' end It works great, until I''m testing and I want to use fixtures.

With the 0.2.0 code, unit testing of workers isn''t working out of the box. I created a bare rails project (dubbed "ninja") and generated one worker "FirstWorker" and did rake test rake test (in /home/joshua/tmp/20061030-bdbtest/ninja) /usr/bin/ruby1.8 -Ilib:test "/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader.rb"

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

I am running Rails 1.1.2 with Ruby 1.82-15. My database is Postgresql. I haven''t had any problems generating models, migrations, using scaffolds, and generally building and using my application, but I haven''t been able to get testing to work. I initially just ignored the problem and kept developing, but would like to add proper testing from here on out. Currently when I type

I have three Rails apps on my laptop. Two can runs tests just fine. The third generates this error when I try to run any tests: > /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/ > active_support/dependencies.rb:200:in `const_missing'': > uninitialized constant Test (NameError) > from ./test/unit/../test_helper.rb:5 > from

hi list - i recently attempted to run rake for a first pass at some tests and ran into a mysterious failure. rake indicated that it had aborted running the tests but provided little information on exactly why this occurred. the only bit of information it did offer was that i could use --trace for a full trace. of course i did that hoping it would provide more detail, but it didn''t help a