Forum: Ruby on Rails Ruby on Rails Fixtures

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Asa (Guest)
on 2006-12-31 01:40
(Received via mailing list)
When I use test fixtures to populate test data into mysql database I am
running into an unexpected behavior.  Only columns explicitly defined
in the fixture is populated into the database.  However, created_on,
created_by, updated_on, updated_by fields along with all fields
normally populated by observers are NULL.  For example, I have a couple
fields that have their values calculated via observers.  I want to test
that these calculations are performed correctly by the observer, so I
don't want to hard code their values in the fixture.

Has anyone else run into this issue?  If so, how did you perform
testing of these fields?  I realize that I could perform these tests
without fixtures by creating and saving the object.  Behind the scenes,
Active Record populates all the fields in the expected manner.  Then I
could find the saved record and assert_equal the expected calculations.
 However this approach seems brittle and I rather use fixtures.  It
doesn't seem (from the results) that I am getting that the fixtures
functionality uses Active Record to serialize data to mysql.

This topic is locked and can not be replied to.