APIv4 - Reorganize test classes, don't use transactions for custom value tests

[civicrm-core.git] / tests / phpunit / api / v4 / Entity / SystemRotateKeyTest.php

diff --git a/tests/phpunit/api/v4/Entity/SystemRotateKeyTest.php b/tests/phpunit/api/v4/Entity/SystemRotateKeyTest.php
index 5244fbd7fc2d29edba8c954640bdeb1325bfa453..0c62c720a9d7e075022f964c1ce0356b41b7e8f5 100644 (file)
--- a/tests/phpunit/api/v4/Entity/SystemRotateKeyTest.php
+++ b/tests/phpunit/api/v4/Entity/SystemRotateKeyTest.php
@@ -19,21 +19,22 @@
 
 namespace api\v4\Entity;
 
-use api\v4\UnitTestCase;
+use api\v4\Api4TestBase;
 use Civi\Crypto\CryptoTestTrait;
+use Civi\Test\TransactionalInterface;
 use Psr\Log\LoggerInterface;
 
 /**
  * @group headless
  */
-class RotateKeyTest extends UnitTestCase {
+class RotateKeyTest extends Api4TestBase implements TransactionalInterface {
 
   use CryptoTestTrait;
 
   /**
    * Set up baseline for testing
    */
-  public function setUp() {
+  public function setUp(): void {
     parent::setUp();
     \CRM_Utils_Hook::singleton()->setHook('civicrm_crypto', [$this, 'registerExampleKeys']);
     \CRM_Utils_Hook::singleton()->setHook('civicrm_cryptoRotateKey', [$this, 'onRotateKey']);