[
https://issues.apache.org/jira/browse/LOG4PHP-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Grobmeier resolved LOG4PHP-49.
----------------------------------------
Resolution: Fixed
Added dry mode to SocketAppender. This enables us to test most of the
functionality without using the acutal socket calls
> Create LoggerAppenderSocket Test
> --------------------------------
>
> Key: LOG4PHP-49
> URL: https://issues.apache.org/jira/browse/LOG4PHP-49
> Project: Log4php
> Issue Type: Improvement
> Components: Tests
> Reporter: Christian Grobmeier
> Fix For: 2.0
>
>
> LoggerAppenderSocket Test must be implemented.
> Knut Urdalen:
> LoggerAppenderSocket is a bit more complicated. It uses fsockopen() to
> connect to a socket. I have written an example using PEAR::Net::Server [4]
> (see examples/client.php and examples/server.php) that I've used as a
> experimental central logging server before. I think it's possible to write a
> unit test case here which startup the socket server and connect with a client
> (but you need to manage two different processes here which is hard in PHP, I
> only know about the pcntl-extension [] used for spawning processes on *nix).
> If you write a test case for this remember to use self::markTestSkipped('With
> some useful message'); [6] if the test case is unable to run because of
> missing dependencies.
> http://www.phpunit.de/manual/3.3/en/incomplete-and-skipped-tests.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
