How to write unit tests with your daemon?

[lifo101]

How to write unit tests with your daemon?

[phuze]

Hi Dave,

Please post code inside of code tags; its not pleasant trying to read that mate.

The behaviour you are describing, admittedly, doesn't make much sense. Just to confirm, are you running this through cli mode?

Are you using tasks, or workers?

What does your daemon execute() function look like?

[phuze]

Upon inspecting the code you tried to post above, i see syntax errors and logic that I don't understand. Why delete the log file every time? You are also trying to execute your code inside a condition based on the existence of a log file which won't exist the second time around since you're deleting it. There's a lot of reasons why your code is failing here.

Did you take a look at the the examples?

logfile = __DIR__ . '/../logs/migrate_posts_service.log';
$this->pidfile = __DIR__ . '/../locks/ALO_Client_Daemon_Migrate_Posts.pid';

if (file_exists($this->logfile))
    unlink($this->logfile);
    $this->mp = ALO_CLI_Daemon_Migrate_Posts::getInstance()
    ->setDaemonize(false)
    ->setLoopInterval(20)
    ->setVerbose(true)
    ->setDebug(true)
    ->setDebugLevel(3)
    ->setLogFile($this->logfile)
    ->run();
    echo "Finished setUp()\n";
}

[lifo101]

If your code is separated into pieces of logic, then you should be able to unit test things w/o even using the Daemon itself. Your unit tests would simply create instances of your objects and call methods you want to test. All, w/o even creating a Daemon instance.

For instance, if you have a worker you want to test, simply create the Worker in your unit test, call whatever methods you need, check the result and move on.

Testing your main daemon loop logic will be harder and I have no suggestions for that. Generally, the logic in your main daemon loop should be as simple as polling a resource for some event to act on. All of your workers and task objects will be what handles the actual work load, which is where most of your testing will be.