On Fri, Oct 10, 2008 at 9:37 AM, Christopher Bailey
<[EMAIL PROTECTED]> wrote:
> I've moved on from this with a bit different approach. But, I also found
> that the "get" (or whichever http method used) call expects the first
> parameter to be an action, so passing in a string that is a path or UR
I've moved on from this with a bit different approach. But, I also found
that the "get" (or whichever http method used) call expects the first
parameter to be an action, so passing in a string that is a path or URL
doesn't work for that.
On Fri, Oct 10, 2008 at 1:04 AM, Matt Wynne <[EMAIL PROTECT
On 9 Oct 2008, at 20:24, Christopher Bailey wrote:
I have a controller test, where I want to do a GET on a page. Our
URL's are complex, and need to be correct (duh, but we allow some
slop, but that causes a redirect which I want to avoid). Anyway, in
my controller test I do a get to the
I have a controller test, where I want to do a GET on a page. Our URL's are
complex, and need to be correct (duh, but we allow some slop, but that
causes a redirect which I want to avoid). Anyway, in my controller test I
do a get to the URL that is produced by a helper method which calls a named
