#674 new
Murray Steele

validations_test.rb: tests make changes to models without reverting them

Reported by Murray Steele | July 22nd, 2008 @ 08:55 AM | in 2.x

Most of the tests in validations_tests take an existing model, give it a new validation and then do some asserts to make sure that the validations work. There is code in setup to blank out the validations for Topic (the model used in most of the tests), however, other models are used and they are not being revertted.

The problem is that any test that is run after validations_test may encounter problems where models can't be saved because of the validations added by validations_test.

Also, the current method of simply zero-ing the validations for Topic before each test isn't the best case for this because Topic does have some default validations (has_many :replies adds a default validate_associated_records_for_replies), so the state of the Topic model going into these validations_tests is wrong. It's also wrong after the last validation_test as either anything that happens inside that test will not be reverted or the default Topic validations are not reset.

The attached patch provides a repair_helper for activerecord tests that currently knows how to:

a) repair validations: will record the validation state of a model class, execute the block and then reset the validations afterward.

b) repair default error messages: will record the default error messages inside ActiveRecord::Errors, execute the block and then reset the default error messages.

These can be called with a block inside a test, or without a block in the context of a test case to supply default setup / teardown callbacks to do the same.

Comments and changes to this ticket

Please Login or create a free account to add a new comment.

You can update this ticket by sending an email to from your email client. (help)

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Source available from github

The Git repository resides at http://github.com/rails

Check out the current development trunk (Edge Rails) with:

git clone git://github.com/rails/rails.git

The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.

Creating a bug report

When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.

Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.

Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".

Shared Ticket Bins

People watching this ticket