Andy Lester

Many times in tests, if one of the basic T:W:M methods fails, there's no point in continuing. If a `->get_ok()` fails, then there's no reason for the test to continue....

Calls to `lacks_id_ok` and `id_exists_ok` give incorrect line numbers if called in a subtest

2

```$ cat foo.t #!/usr/bin/perl use warnings; use strict; use 5.010; use Test::WWW::Mechanize; use Test::More; my $agent = Test::WWW::Mechanize->new; $agent->update_html( join( '', ) ); $agent->lacks_id_ok( 'exists' ); $agent->id_exists_ok( 'does-not-exist' ); subtest...

Sometimes you may want a global cache for image status across all objects. Sometimes you may want it to be only perl Mech. Allow both of these.

For the sake of speed, `id_exists` makes a big shortcut: ``` my $found = index( $html, " id=\"$id\"" ); if ( $found < 0 ) { $found = index( $html,...

We should do proper Test::Builder::Tester testing of the subtest functions.

We don't check that the request is doing the right thing with click_ok. We need to validate the button, and validate the button+x+y.

Passing an undef as the value to scraped_id_is should fail with an explicit message about "Hey, you can't pass undef as a value."