On 8/15/06, Fergal Daly <[EMAIL PROTECTED]> wrote:
On 15/08/06, Collin Winter <[EMAIL PROTECTED]> wrote:
> The TestCase *classes* are groups of tests, but each TestCase
> *instance* is only a single test, meaning that
> ``str(TestCase('somemethod_name'))`` would
On 8/15/06, Fergal Daly <[EMAIL PROTECTED]> wrote:
On 15/08/06, Collin Winter <[EMAIL PROTECTED]> wrote:
> The solution to this particular issue would be to have your SomeTest
> class override TestCase.id(), TestCase.__str__() and/or
> TestCase.__repr__() to take into accou
end on being run in a
certain order.
Collin Winter
tests in my test suite, so I'll pull all tests from my
test modules into a suite (or suite-of-suites)". In my experience, the
more important hierarchical information is of the form
$module_name.$test_case_name.$test_method_name, which TAP can handle.
What has your experience been?
Collin Winter
coding up
such a thing has been on my todo list for a week or two now.
Collin Winter
when you passed it to B::Deparse
whether $five was 5 or 6? So, as you said in your post, "the deparsed
subs are identical they may behave totally differently"; do they
really behave differently, though? They both check parent scopes for
unknown variables; the only difference is where they're checking.
Collin Winter
this matter sorted, I've started on the code
and requisite tests to make the new stuff work.
Collin Winter
nto the works. Storable uses B::Deparse when
serialising coderefs, though, so I'm certain there's a way around
this.
Collin Winter
On 6/25/05, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> Currently, throwing is_deeply() a code ref causes it to barf.
>
> perl -MTest:
