Files
piratepoet/tests/integration/Cron/Triggers/MailPoetTest.php
Rostislav Wolny ff238bf69a Refactor MailPoet\Cron to use new settings
[MAILPOET-1757]
2019-01-31 15:57:58 +01:00

36 lines
1.1 KiB
PHP

<?php
namespace MailPoet\Cron\Triggers;
use MailPoet\API\JSON\Endpoints\Cron;
use MailPoet\Cron\CronHelper;
use MailPoet\Cron\Triggers\MailPoet;
use MailPoet\Models\Setting;
use MailPoet\Settings\SettingsController;
class MailPoetTest extends \MailPoetTest {
/** @var SettingsController */
private $settings;
function _before() {
parent::_before();
// cron trigger is by default set to 'WordPress'; when it runs and does not
// detect any queues to process, it deletes the daemon setting, so Supervisor that's
// called by the MailPoet cron trigger does not work. for that matter, we need to set
// the trigger setting to anything but 'WordPress'.
$this->settings = new SettingsController();
$this->settings->set('cron_trigger', array(
'method' => 'none'
));
}
function testItCanRun() {
expect($this->settings->get(CronHelper::DAEMON_SETTING))->null();
MailPoet::run();
expect($this->settings->get(CronHelper::DAEMON_SETTING))->notEmpty();
}
function _after() {
\ORM::raw_execute('TRUNCATE ' . Setting::$_table);
}
}