similar to: Integration testing without loading fixtures

Functional tests properly load fixtures, but my integration test chokes: # def self.create_fixtures(fixtures_directory, table_names, class_names = {}) # puts("fixtures dir: "+(fixtures_directory.nil? ? "nil" : fixtures_directory)) It''s only nil for my integration tests. I''m on rails edge. Does anyone know what I''m doing wrong here? 1) Error:

Hallo -- I have the most bizzare problem. I have a test called PropertyTest that runs absolutely fine. Even if I totally clear the test database before running it, it happily scoots off, loads all necessary fixtures, runs & passes all tests. My problem arises when I run rake test:units. Then, all other tests pass fine, but this one starts failing as if the fixture data simply

Hi all. I have a question on accessing fixtures by name. I''m doing integration testing very similar to what is described in Jamis''s excellent writeup at http://jamis.jamisbuck.org/articles/2006/03/09/integration-testing-in-rails-1-1. The problem is that I am using ordered yml fixtures so that rake loads each element in the correct sequence. I need to do this because my

Any idea why this fixture would fail to load any data? <% %w( Admin Pharmacist PI/Co-PI Research\ Nurse ).each { |g| Group.create( :name => g ) } %> It works perfectly in irb but when I do rake db:fixtures:load I get no data, no errors, and no error logs. I realize my fixture doesn''t look like your typical run-of-the-mill fixture but it''s that way because I''m

Yo guys... I''m starting to get into testing my current e-commerce Rails app before I Engine-ify it...(Codename "Substruct" - don''t sleep!) I''ve got some data that should be loaded before each test. Convention tells me that I should prepare this data in nice YML files as fixtures, although I''m not quite so sure. The data in question is a country list

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 =>

Hi, I''m new to rspec. I have some fixtures in /spec/fixtures. If they were in /test/fixtures they could be loaded with rake db:fixtures:load. Is there any way other than a symlink to load my rspec fixtures into the database with rake? Or, can I cause rspec to load the fixtures from /test/fixtures? Thanks, Paul

I''ve got an interesting (possibly) problem right now between autotest and rails integration tests. There are a few things to preface this with. Works fine: rake test rake test:integration Blows up: autotest Autotest is correctly determining rails and runs tests just fine. One part of the behavior is that if I save a change in just the integration test (even hitting cmd+s to trigger a

Hi, I have a strange problem with testing classes which have a HABTM relation. It seems that while running my tests with rake the fixture for the association table is not loaded - as a result I get a failure on a test which simply checks the number of associated elements - it says it''s 0 although there should be one. The weird thing is that when I run the tests with rcov

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

I am attempting to do selective fixture loading against my test database. When I run rake db:fixtures:load FIXTURES=DataSetInfo I get no output. (A full trace is below). I''m trying to figure out why nothing happens. 1) Does the command above attempt to operate against my test database? 2) DataSetInfo is the name of my table and the name of my yml file I generated these YAML

I''m running Rails 3 and I''m trying to populate a table using rake db:fixtures:load, and I''m getting a "Could not find" file error. The table is called stores, and I''ve confirmed that it exists, and the data is in stores.yml in my test/fixtures directory. The command I''m running is rake db:fixtures:load FIXTURES=stores. The error message

Hello, I have a table of zipcodes that I am using in my application, so there are approximately 50,000 rows in this table. I have dumped the table to a fixture yaml file to represent this data, but when I try to load it, I get this error: SystemStackError: stack level too deep Is there a max size allowed for a fixture file..? Here is the --trace output: rake db:fixtures:load --trace **

I''m starting to write some rather intricate billing logic, the test data for which will almost certainly overwhelm my standard set of test fixtures, leading to a test maintenance nightmare. I''d like to be able to specify that some test classes load their fixtures from a different location, but I can''t seem to get it to work. I did see this post from last December:

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

What are the semantics of the fixtures idea? I have a set of unit tests that when I run individually run fine. When I run them under "rake", the second unit test to call the same fixture doesn''t seem to actually load the data. That is, I have 2 tests; test1.rb and test2.rb, and each one calls "fixtures :foo". test1 runs, by itself, then test2 fails because it

Hi, I don''t know if this was obvious to anyone else but for ages I never knew how to load binary data into fixtures (like images) except via separate rake tasks. I just figured it out so I figured I would share info with people - it is written up at; http://www.realityforge.org/articles/2006/04/06/loading-binary-data-into-rails-fixtures -- Cheers, Peter Donald

How do a test a rake task using fixtures? I''ve written yaml files for each fixture but I''m not sure how to test the rake using the fixtures. -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe

= Description This plugin is a super lightweight tool used to export data into the test/fixtures directory. So if you want to export all your data from your production server into your development environment, this will simplify the process without having to load up your database manager. [%] rake db:fixtures:export_all RAILS_ENV=development [%] rake db:fixtures:load = INSTALLATION

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