# Fixtures not reloading for every test

**URL:** <https://www.ruby-forum.com/t/fixtures-not-reloading-for-every-test/117143>\
**Category:** Rails\
**Created:** [October 13, 2007, 8:39pm UTC](https://www.ruby-forum.com/t/fixtures-not-reloading-for-every-test/117143 "2007-10-13T20:39:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stickstone](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/6f9a4e/32.png) [@stickstone](https://www.ruby-forum.com/u/stickstone)\
**Post date:** [October 13, 2007, 8:39pm UTC](https://www.ruby-forum.com/t/fixtures-not-reloading-for-every-test/117143/1 "2007-10-13T20:39:34Z")

</div>

For some reason my fixtures are not reloading their data after each test  
method. I’ve read that this is supposed to be the case so that I can  
work with clean data for every test, but it isn’t happening. I have  
checked my test test.rb configuration environment file and have not  
noticed anything out of place. There is nothing in the API that I have  
come across that would create this behavior. Any help?

---

<div class="post-metadata">

**Author:** ![stickstone](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/6f9a4e/32.png) [@stickstone](https://www.ruby-forum.com/u/stickstone)\
**Post date:** [October 14, 2007, 7:53am UTC](https://www.ruby-forum.com/t/fixtures-not-reloading-for-every-test/117143/2 "2007-10-14T07:53:38Z")

</div>

I found the answer if anybody else runs into this issue. Check your  
test\_helper.rb file. Mine has transactional fixtures turned on:

self.use\_transactional\_fixtures = true

Just set that line to false and that should fix things.

Brian C. wrote:

> For some reason my fixtures are not reloading their data after each test  
> method. I’ve read that this is supposed to be the case so that I can  
> work with clean data for every test, but it isn’t happening. I have  
> checked my test test.rb configuration environment file and have not  
> noticed anything out of place. There is nothing in the API that I have  
> come across that would create this behavior. Any help?
