[Catalyst-dev] Catalyst test suite
Andy Grundman
andy at hybridized.org
Tue May 6 17:46:01 BST 2008
I guess we weren't testing the same thing... I was running t/
optional_http-server.t not the POE test. BTW, the POE engine is no
longer supported (by me anyway), it's been deprecated in favor of the
HTTP::Prefork engine.
On May 6, 2008, at 12:41 PM, Yuri Shtil wrote:
> I just fetched the trunk (am not sure whether it is 5.7) and got the
> same:
>
> 'Couldn\'t load plugin "Catalyst::Plugin::
> +TestApp::Plugin::FullyQualified", "Can\'t locate Catalyst/Plugin/
> +TestApp/Plugin/FullyQualified.pm in @INC (@INC contains: /export/
> work/CatRepo/trunk/Catalyst-Engine-HTTP-POE/t/tmp/TestApp/script/../
> lib /export/work/CatRepo/trunk/Catalyst-Engine-HTTP-POE/t/../lib /
> usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/
> site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/
> 5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-
> linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/
> site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/
> site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/
> 5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-
> linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-
> thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-
> multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/
> 5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/
> 5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-
> thread-multi /usr/lib/perl5/5.8.8 .) at /usr/lib/perl5/site_perl/
> 5.8.8/Catalyst.pm line 1752.
>
> BTW the optional_poe-server.t script goes into an infinite loop, I
> had to read the pipe to see this.
>
> What do I miss?
>
> Where does Catalyst::Plugin::+TestApp::Plugin::FullyQualified come
> from?
>
> Andy Grundman wrote:
>> I just tried it with 5.7 trunk and it worked fine for me.
>>
>> On May 6, 2008, at 11:23 AM, Yuri Shtil wrote:
>>
>>> Hi Andy,
>>> I was trying to run t/optional_http-server.t. as you advised and
>>> got:
>>>
>>> Couldn't load plugin "Catalyst::Plugin::
>>> +TestApp::Plugin::FullyQualified
>>>
>>> What is this plus?
>>>
>>> Andy Grundman wrote:
>>>>
>>>> On May 5, 2008, at 7:48 PM, Yuri Shtil wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am contemplating to write a new Catalyst::Engine subclass. A
>>>>> looked at the test suite of an existing module
>>>>> ( Catalyst::Engine::HTTP::POE) and discovered a lot of *.pm and
>>>>> testapp_poe.pl. I could not run it since some modules were
>>>>> missing (like +TestApp::Plugin::FullyQualified).
>>>>>
>>>>> The POD also referred to this module passing "the Catalyst test
>>>>> suite".
>>>>>
>>>>> Am I missing something needed to develop and test
>>>>> Catalyst::Engine? How do I get and use the test suite?
>>>>
>>>> Hi,
>>>>
>>>> The Catalyst test suite for engines consists of the t/live_*
>>>> files. There are several ways to run these tests against your
>>>> engine.
>>>>
>>>> If your engine can be scripted to run automatically, you can
>>>> write a wrapper script that launches the engine and runs all the
>>>> tests against it. For an example of this see t/optional_http-
>>>> server.t.
>>>>
>>>> You can manually run tests against your engine by setting the
>>>> CATALYST_SERVER env var to the URI where your engine is running.
>>>> Then any Catalyst tests you run will run against that host. This
>>>> is very helpful for debugging a single failing test. Note that
>>>> your engine must be running the TestApp, which just means you
>>>> need to copy t/lib/* into an app.
>>>>
>>>> -Andy
>>>>
>>
More information about the Catalyst-dev
mailing list