--- author: email: ash@firemirror.com keyid: bfc7465ebdca5337 name: Ash Berlin categories: [] date: 2007-09-05T12:49:07Z guid: 5B4C0FBC-5B99-11DC-94D7-AB27370D5E4E modified: 2007-09-05T12:49:07Z raw: "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nLast week at YAPC::EU I saw a few interesting talks, including Stevan's [Moose](http://www.iinteractive.com/moose/yapc_eu_2007_slides/start.html) introduction. I found this talk really helpful, maybe in part because I had read through Moose's documentation and cookbook examples once a month or so ago.\n\nSo I wanted to learn Moose a bit better, and I'm a firm believer of learning new technologies by actually writing something using them, so I needed a project - not to complex, but also not trivial. And I had just the thing - something I made a start on in June, but sadly only ever existed on my laptop that got stolen. I present the following code snippet for consideration taken from a test suite at work:\n\n lang:perl\n my $mech = WWW::Mechanize->new;\n\n ok( $mech->get(\"$base/index\") );\n ok( $mech->content =~ m{
Welcome To My Site
} );\n\nWhat's wrong with it? Well for a start, it should be using Test::WWW::Mechanize which fixes a few problems. But its still parsing XHTML (you *do* write XHTML web sites don't you.) using a regexp, which is always a bad idea. What happens if you change the ID of the element, or add a class to it? It'll stop working and your tests will break. My solution? [WWW::Mechanize::TreeBuilder](http://search.cpan.org/dist/WWW-Mechanize-TreeBuilder/lib/WWW/Mechanize/TreeBuilder.pm):\n\n\n lang:perl\n my $mech = Test::WWW::Mechanize->new;\n WWW::Mechanize::TreeBuilder->meta->apply($mech);\n\n $mech->get_ok(\"$base/index\");\n is( $mech->look_down(_tag => 'div', id => 'header')->as_trimmed_text, 'Welcome To My Site');\n\nMuch better.\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.7 (Darwin)\n\niD8DBQFG3qdSv8dGXr3KUzcRAkvnAJ9rXeqgm0GJy8f0hi3M373REu6X4QCfcBnv\njAS13SadFxbyLKwGY8tf8hQ=\n=cbld\n-----END PGP SIGNATURE-----\n" signed: 1 summary: " Last week at YAPC::EU I saw a few interesting …" tags: - perl: 0 - testing: 0 - cpan: 0 - moose: 0 text: "\nLast week at YAPC::EU I saw a few interesting talks, including Stevan's\nMoose [1] introduction. I found this talk really helpful, maybe in part\nbecause I had read through Moose's documentation and cookbook examples\nonce a month or so ago.\n\nSo I wanted to learn Moose a bit better, and I'm a firm believer of\nlearning new technologies by actually writing something using them, so I\nneeded a project - not to complex, but also not trivial. And I had just\nthe thing - something I made a start on in June, but sadly only ever ex-\nisted on my laptop that got stolen. I present the following code snippet\nfor consideration taken from a test suite at work:\n\nWhat's wrong with it? Well for a start, it should be using\nTest::WWW::Mechanize which fixes a few problems. But its still parsing\nXHTML (you do write XHTML web sites don't you.) using a regexp, which is\nalways a bad idea. What happens if you change the ID of the element, or\nadd a class to it? It'll stop working and your tests will break. My so-\nlution? WWW::Mechanize::TreeBuilder [2]:\n\nMuch better.\n\n-- \n [1] http://www.iinteractive.com/moose/yapc_eu_2007_slides/start.html\n [2] http://search.cpan.org/dist/WWW-Mechanize-\n TreeBuilder/lib/WWW/Mechanize/TreeBuilder.pm\n" title: WWW::Mechanize::TreeBuilder type: markdown uri: http://perlitist.com/articles/www-mechanize-treebuilder xhtml: "

Last week at YAPC::EU I saw a few interesting talks, including Stevan's Moose introduction. I found this talk really helpful, maybe in part because I had read through Moose's documentation and cookbook examples once a month or so ago.

So I wanted to learn Moose a bit better, and I'm a firm believer of learning new technologies by actually writing something using them, so I needed a project - not to complex, but also not trivial. And I had just the thing - something I made a start on in June, but sadly only ever existed on my laptop that got stolen. I present the following code snippet for consideration taken from a test suite at work:

my $mech = WWW::Mechanize->new;\n\nok( $mech->get("$base/index") );\nok( $mech->content =~ m{<div id="header">Welcome To My Site</div>} );\n

What's wrong with it? Well for a start, it should be using Test::WWW::Mechanize which fixes a few problems. But its still parsing XHTML (you do write XHTML web sites don't you.) using a regexp, which is always a bad idea. What happens if you change the ID of the element, or add a class to it? It'll stop working and your tests will break. My solution? WWW::Mechanize::TreeBuilder:

my $mech = Test::WWW::Mechanize->new;\nWWW::Mechanize::TreeBuilder->meta->apply($mech);\n\n$mech->get_ok("$base/index");\nis( $mech->look_down(_tag => 'div', id => 'header')->as_trimmed_text, 'Welcome To My Site');\n

Much better.

"