# Goldberg breaks (almost) all functional tests

**URL:** <https://www.ruby-forum.com/t/goldberg-breaks-almost-all-functional-tests/166903>\
**Category:** Rails\
**Created:** [April 30, 2009, 6:54pm UTC](https://www.ruby-forum.com/t/goldberg-breaks-almost-all-functional-tests/166903 "2009-04-30T18:54:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Commander\_J](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/a8b319/32.png) [@Commander\_J](https://www.ruby-forum.com/u/Commander_J)\
**Post date:** [April 30, 2009, 6:54pm UTC](https://www.ruby-forum.com/t/goldberg-breaks-almost-all-functional-tests/166903/1 "2009-04-30T18:54:33Z")

</div>

Anyone else have that if you protect certain actions with Goldberg, you  
can’t test them anymore?

I know some of you are using Goldberg today so how did you manage that?  
Keep  
the controllers as simple as possible? Test them yourself?

Options include:

- Log in a Goldberg user before loading test suite (seems the least  
obtrusive solution)
- Keep a different project version without the plugin (breaks template  
references such as goldberg\_title and goldberg\_menu)
- Filter out the security mechanism in test mode (breaks Goldberg’s own  
tests)

---

<div class="post-metadata">

**Author:** ![Commander\_J](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/a8b319/32.png) [@Commander\_J](https://www.ruby-forum.com/u/Commander_J)\
**Post date:** [April 30, 2009, 6:59pm UTC](https://www.ruby-forum.com/t/goldberg-breaks-almost-all-functional-tests/166903/2 "2009-04-30T18:59:49Z")

</div>

I just found out that I double posted! Please excuse me for that.

On Thu, Apr 30, 2009 at 6:53 PM, Commander J. \<