Goldberg breaks (almost) all functional tests

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?
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

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

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

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs