Comments on: Testing Single Table Inheritance Models in Ruby on Rails

By: davidg

davidg — Sat, 29 May 2010 05:04:54 +0000

Appreciate it! Single table inheritance models blew up my unit tests starting out – thanks for the quick and easy fix.

By: Supra shoes

Supra shoes — Fri, 23 Apr 2010 04:33:57 +0000

Wonderful journey and experience!

By: Vanne

Vanne — Fri, 20 Jun 2008 17:57:11 +0000

@Laurent

Got the same problem. Turns out fixtures were generated for all models.
So for the table that is really there but also for the models which inherit from it, which obviously don’t have a table, as that is the whole point of STI.
The scaffold generator does create fixtures even if you specify –skip-migration it seems.

By: Dave Hrycyszyn

Dave Hrycyszyn — Tue, 10 Jun 2008 16:50:39 +0000

One thing that could cause this is if you forgot to change the

fixtures :modules

line from your test into

fixtures :applications # or whatever your table name is

By: Laurent

Laurent — Sun, 01 Jun 2008 07:32:38 +0000

I have a problem in my test .
When launching the test on my model ‘Module’ inherited from a class ‘Application’ (the table applications exist in database)
My test tries first to clean the table ‘modules’ , that does not exist.
Did i miss something?

By: Dave

Dave — Wed, 07 May 2008 16:43:59 +0000

inflect.uncountable would do the job instead of set_table_name, yeah, but all the fixtures work is always necessary (so articles.yml is still useless, and you need to put your articles fixtures into the content.yml fixture with a type property, etc).

By: Brandon Zylstra

Brandon Zylstra — Fri, 28 Mar 2008 17:39:21 +0000

Wouldn’t it also have worked (with less work manually changing tests) to add a line to your inflections.rb like so:
inflect.uncountable %w( fish sheep content )

By: Kamil

Kamil — Mon, 03 Dec 2007 19:54:28 +0000

Thanks, it helped