Hi Ash, Everyone,
Thanks, that seemed to move me along further. I'm still unable to get
the content part of the POST. I'm able to send the username and
password through, but for some reason my controller gets empty
content. Here is the request I've formed:
##### with mech object
my $t1 = Test::WWW::Mechanize::Catalyst->new;
$t1->add_header( 'Content-type' => 'text/x-json' );
$req = new HTTP::Request ("POST", "http://localhost/rest/something";,
['X-Username' => 'xxxxx',
'X-Password' => 'xxxxx'],
to_json({ stuff })
);
$res = $t1->request( $req );
### fails with my Bad Request
#### end
In the above request, username and password are processed
successfully, but no content is received. I look for the content in
$c->req->data.
Here is the analogous LWP request:
##### LWP object
$ua = new LWP::UserAgent;
$req = new HTTP::Request ("POST", "http://localhost:3000/rest/
something",
['X-Username' => 'xxxxx',
'X-Password' => 'xxxxx'],
to_json({ stuff })
);
$req->content_type('text/x-json');
$res = $ua->request($req);
### successfully creates the object
#### end
This works fine and creates the object.
It seems like the content is not getting passed through to controller
when using Mechanize. Any thoughts?
Thanks,
Damon
On Feb 26, 2008, at 12:23 PM, Ash Berlin wrote:
On 26 Feb 2008, at 20:20, Damon Snyder wrote:
Hi Everyone,
I'm developing a Catalyst::Controller::REST based controller in an
app that I'm working on. I've created the _GET and _POST methods
and now I'm trying to test them. They work fine if I test them
using curl from the command line or LWP::UserAgent, but now I'm
trying to add tests for them using Test::WWW::Mechanize::Catalyst.
I'm having a hard time getting Test::WWW::Mechanize::Catalyst to
interact my REST controller. I can build the request fine with
HTTP::Request and LWP::UserAgent, but I can't seem to get it to
work with Test::WWW::Mechanize::Catalyst. Does anyone have any
example code where they were able to get the GET, POST, and PUT to
test successfully using Test::WWW::Mechanize::Catalyst?
Here is the basic construction of the POST with LWP::UserAgent and
Test::More:
my $ua = new LWP::UserAgent;
$ua->default_header( 'X-Username' => 'xxxx', 'X-Password' =>
'xxxxx' );
#my $req = new HTTP::Request POST => "http://localhost/rest/
something";
$req->content_type('text/x-json');
$req->content(to_json(( { name => "bla", foo => "haaa" } ));
my $res = $ua->request($req);
ok($res, "Request was successful");
ok($res->headers->{status} == 201);
my $something = from_json($res->content);
ok($something->{foo} eq 'haaa');
I could continue with LWP::UserAgent, but it seems easier and more
maintainable to use the catalyst mechanize route if possible
(testing against other servers, don't need local server running etc).
Thanks,
Damon
sub make_json_request {
my ($self, $uri, $data) = @_;
my $req = POST( $uri,
Content_Type => 'text/json',
Content => $self->to_json($data)
);
my $res = $self->mech->request($req);
return unless $res->code == 200;
die "JSON request returned 200 but not correct Content-Type
(@{[$res->content_type]})"
unless $res->header('Content-Type') eq 'text/javascript';
return $self->from_json($res->content);
}
$self->mech returns a Test:WWW::Mechanize::Catalyst instance.
POST method comes from
use HTTP::Request::Common;
Not that disimilar from what you had, just notice that $mech-
>request will take a HTTP::Request object as well as just a URI.
Ash
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
Damon Snyder
www.influxMEDIA.com
(888) 266 6728 x1011
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
