From ccdf6bd5fe7f9325d230931eec55a74ea27cfa53 Mon Sep 17 00:00:00 2001 From: Tim Otten Date: Sun, 27 Sep 2015 09:53:11 -0400 Subject: [PATCH] CRM-13422 - ActionScheduleTest - Loosen domain token handling Discussed with a few people -- neither the contact nor the scheduled reminder has a domain_id, so it seems hard to define a clear handling of domain tokens. --- tests/phpunit/CRM/Core/BAO/ActionScheduleTest.php | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tests/phpunit/CRM/Core/BAO/ActionScheduleTest.php b/tests/phpunit/CRM/Core/BAO/ActionScheduleTest.php index be1d3cba16..e8fa0d7825 100755 --- a/tests/phpunit/CRM/Core/BAO/ActionScheduleTest.php +++ b/tests/phpunit/CRM/Core/BAO/ActionScheduleTest.php @@ -608,7 +608,9 @@ class CRM_Core_BAO_ActionScheduleTest extends CiviUnitTestCase { '{domain.name}', // domain token '{activity.activity_type}', // action-scheduler token )); - $manyTokensExpected = 'test-member@example.com;;Female;;Female;;Second Domain;;Phone Call'; + // Note: The behavior of domain-tokens on a scheduled reminder is undefined. All we + // can really do is check that it has something. + $manyTokensExpected = 'test-member@example.com;;Female;;Female;;[a-zA-Z0-9 ]+;;Phone Call'; // In this example, we use a lot of tokens cutting across multiple components.. $cases[0] = array( -- 2.25.1