similar to: Model syntax errors obscured during fixture load

When I run rake against Rails 8.5 to test unaltered model tests with yaml fixtures I get the error and stack trace reproduced below for every one of my model objects. Has anyone seen something this before? Any idea what could be going on here? The following ruby-talk thread may or may not be relevant: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/95301. Thanks much,

On Fri, 22 Oct 2004 10:58:16 -0700, Bob Sidebotham <bob@windsong.bc.ca> wrote: > Do you expect to release api docs for 1.2? Bob has already followed up and noted that he found the RDoc sources for the FXRuby 1.2 API documentation, but I''ll also note that you can already link to those docs online, here: http://www.fxruby.org/1.2/doc/api I''m probably going to go

On Fri, 22 Oct 2004 13:39:06 -0700, Bob Sidebotham <bob@windsong.bc.ca> wrote: > In 1.2 FXTable, numColumns is documented as numCols, but should be > numColumns, I think. Also the examples/table.rb app uses numCols, and > should use numColumns. Yes, you''re right. I''ve added both of these bugs to the FXRuby bug list, found here:

> I was trying to run Unicorn 4.5.0''s tests and I''m getting this. Am I doing something wrong? > > [vagrant at localhost unicorn-4.5.0]$ testrb -Ilib -Iext/unicorn_http -I. test > /home/vagrant/.gem/ruby/1.9.1/gems/unicorn-4.5.0/test/unit/test_tee_input.rb:7:in `<top (required)>'': superclass mismatch for class TeeInput (TypeError) > from

I''m finally getting beyond using basic test fixtures, and a few questions have popped up. Has anyone found ways to do these? 1. Use a test fixture that is named differently from its table name? We''d like to have more than one possible fixture per table. (Or perhaps use test fixtures named similarly but in different directories.) 2. Load a test fixture for one test method only

I am trying to understand some rake stuff better .. I have a test that works fine if I do: "ruby test/integration/tcp_test.rb -n test_job_create" but if I try to do it in a rake file like below, it errors out. It seems the t.options is the problem because I can get it to work without that: /usr/bin/ruby -I"lib" "/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/

I want to put multiple plots on a page using par(mfrow), then a single title at the top. This should work, but doesn't: R> par(oma=c(0,0,4,0), mfrow=c(3,4)) R> for (i in 1:12) {plot(1); title(i)} R> ## text(10,10, ".") R> par(mfrow=c(1,1), oma=c(0,0,1,0)) R> title("Main Title") The main title does not appear. However, uncommenting the third line

I just installed 1.9.2 on my 2nd machine, but after I installed I checked the version with ruby -v and it sent me 1.8.7 Here''s the terminal output...anyone know what''s wrong (I have RVM installed): Francescas-MacBook-Air:~ fkrihely$ rvm install 1.9.2 Fetching yaml-0.1.4.tar.gz to /Users/fkrihely/.rvm/archives Extracting yaml-0.1.4.tar.gz to /Users/fkrihely/.rvm/src Configuring

I am trying to create unit tests for my users model but when I add a test that destroys a user, that user is not available in any of the other test. If I remove the test that destroys the user all my other tests work again. All the fixtures are suppose be reloaded between tests right? Here is my testcase : require File.dirname(__FILE__) + ''/../test_helper'' class UserTest

In a functional test, I want to call an action in another controller (a login) before testing things in the current controller. As far as I can tell from the extremely sparse documentation and the AWDR book, this seems to be impossible. The post() functions takes an action argument only, and that''s that. Surely I must be misunderstanding things? -- Calle Dybedahl

Hello, i am trying to fix the code for fixtures in rails because it is buggy and internal variable names are confusing, could somebody please explain to me what is the intended purpose of Fixture and Fixtures classes respectively? For example, why do we need both `Fixtures.initialize`and `Fixture.initialize`? They both "initialize" a single fixture, and in fact `Fixture.initialize`

I have found useful to have the table information associated to models disp?ayed in the models and fixtures files of my rails applications. If you want to add this information to the spec_fixtures and specs add the following patch to your plugin. Index: vendor/plugins/annotate_models/lib/annotate_models.rb =================================================================== ---

I''m running into a problem where one of my fixtures uses ERb to get an id for a row that isn''t created yet. In setup, I create that row. Since it appears that fixtures are loaded before setup is run, that''s a problem. I can''t put the row creation in a fixture - its part of the business rules of one of my models. Anyone know how to load a fixture manually

Hello all, I have a fixture under folder-grouping : ./fixtures/foo/bars.yml I need to reference the data in bars during functional test. methods.sort reveals ''foo/bars'' as a method in the current context (breakpointed), but I don''t know how to reference a method called ''foo/bars''. - OR - how should i reference the fixture when I''m using

Hi, I have problem accessing the testfixture. The values from the YML-Fixture-File are correctly written into database, but accessing the fixture is impossible. It is always nil. Is anything wrong with this test? class MyModelTest < Test::Unit::TestCase fixtures :my_model def test_simple a = MyModel.find(@my_model["first"].id) # Accessing @my_model is impossible ...

Hi All: I develop on several machines, most have Mysql 4.* and one has Mysql 5.0. On 4.*, the following erb for a fixture works fine: updated_at: <%= 1.days.ago.to_s:db%> But fails on 5.0. I had a similar deal when I had date fixtures, and switched forrmats so that both 4.* and 5.0 were happy. is there to_s:db_works_for_mysql_50() ? or similar? Thanks Forrest

I''m following Agile Edition 1. On page 148 it suggests using instance variables named after the fixture, for example: assert_equal @version_control_book.id, @product.id When I introduce this type of instance variable into my test, I get the following error: 1) Error: test_not_owner(GroupTest): RuntimeError: Called id for nil, which would mistakenly be 4 -- if you really wanted the

Hi, I am following the Agile Web Development with Rails book and it looks like either book is wrong or edge rails are broken. I am trying to access fixture data through instance shortcuts. I.e. customers.yml through @customers and it is not assigned. Anybody knows why? Sergei -- Posted via http://www.ruby-forum.com/.

OK, we all know that Rails turned off instantiated fixtures by default in 1.0. That''s not a problem. However, what I''m now wondering is how to access the raw fixture data out of the YML file (as opposed to the database.) Mainly, for comparing my database results with my expected results in a DRY way. The book says if you have the command "fixtures :foo", that

Hi, I want to add the basic model record create tests for my rails app as in the "Agile Web Development with Rails" example: i.e. (header stuff and boring repitition missed) def test_create assert_kind_of Requirement, requirements(:requirement_1) assert_equal <at>requirements["requirement_1"]["name"], requirements(:requirement_1).name end Now I''m