On Thu, Sep 02, 2004 at 08:03:01AM -0400, Geoffrey Young wrote:
> you could do both - test-driven development. personally, I don't know how I
> ever got along without Apache-Test, for both development and debugging. how
> I wrote applications before seemed insane when compared to using the tools
Thomas Lochmatter wrote:
> Thanks for the hint. I didn't know about Apache::Test. It
> seems to be a quite big testing framework.
it can be big or small, depending on what you need it to be :)
> I use Apache::FakeRequest for debugging (while developing)
> rather than for testing.
you could do
Thanks for the hint. I didn't know about Apache::Test. It
seems to be a quite big testing framework.
I use Apache::FakeRequest for debugging (while developing)
rather than for testing. The advantage is that it's very
simple/small/handy and does exactly what I need: a fake
Apache object replacement
Thomas Lochmatter wrote:
> You're right: both methods (content_languages() and
> content_language()) work on the Apache object, although
> only content_languages() is documented (perldoc Apache)!
>
> Since Apache::FakeRequest wants to be a complete fake
> object, it should implement both methods
You're right: both methods (content_languages() and
content_language()) work on the Apache object, although
only content_languages() is documented (perldoc Apache)!
Since Apache::FakeRequest wants to be a complete fake
object, it should implement both methods as well, I think.
Hence, the patch wou
Thomas Lochmatter wrote:
(ModPerl 1.29, Apache.pm 1.27, FakeRequest.pm 1.00)
In the Apache::FakeRequest module, there is a method called
"content_language". The Apache module however calls this
method "content_languages".
I guess this is a bug. It could be corrected by changing
FakeRequest.pm, line
