They work, but we needed to have our existing 0.9.7 Pylons applications to work and they don't access config objects via TestResponse. In fact 90% of our tests are units, i.e. they don't issue request/response, they just do "from pylons import config" and test business logic in isolation from request/response machinery.
Well, anyway - the workaround posted here works fine, but in the future (1.1?) we should consider never leaving pylons.config in this "half-constructed" stage after setup_app(). Cheers, Ev The instructions documented here don't work? > http://pylonshq.com/docs/en/1.0/testing/#testing-pylons-objects > > I can pull config, app_globals, etc. off the response as shown there just > fine. That isn't working for other folks? > > In particular I'm referring to: > http://pylonshq.com/docs/en/1.0/testing/#accessing-special-globals > > Which specifically indicates how to get to the Pylons globals for the > purpose of getting app_globals or config. > > I plan on making the test_app setup process also populate the app_globals > and config global objects, but that didn't make it for 1.0, most likely > it'll be in for 1.0.1 or 1.1. So in the meantime I did try to fully document > how to access these things. > > Cheers, > Ben > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<pylons-discuss%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
