Hi Yehuda, I try do this: http://www.pastie.org/401017
So the first test which tests the whole stack for correct output from the controller pass. The request() runs through whole app, rack and everything is set. The second test tests if the header is set. I thought that this could be the way how to test it because I thought that the environment from app (request.env) is available in response from request(). Maybe I'm doing all this wrong and there is a better way how to share data between different Rack middleware. Maybe I should not test response.original_env in whole stack tests but in the middleware tests. Because the whole stack test pass. Is it actually possible to get Merb::Request object in tests somehow? So I can use request.env['xy'] in tests as in controller? Pavel On Feb 25, 6:49 pm, Yehuda Katz <[email protected]> wrote: > Can you be more clear about what you're trying to do? > > -- Yehuda > > 2009/2/25 Pavel Kunc <[email protected]> > > > > > Hi, > > > I've rack app which sets some headers to env. I thought that request() > > method reuse original Rack environment or pass it as original_env. But > > this doesn't happen. > > > The request() just create new rack app with new env. Is it bug or > > feature? > > > Thanks > > > Pavel > > -- > Yehuda Katz > Developer | Engine Yard > (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
