PHPUnit Testing Best Practices
PHPUnit Test af bedste praksis i XOOPS
Sektion kaldt “PHPUnit Test af bedste praksis i XOOPS”Test er afgørende for at sikre kodekvalitet, forhindre regression og muliggøre sikker refactoring.
Installerer PHPUnit
Sektion kaldt “Installerer PHPUnit”# Using Composercomposer require --dev phpunit/phpunit ^9.0
# Run tests./vendor/bin/phpunitphpunit.xml Konfiguration
Sektion kaldt “phpunit.xml Konfiguration”<?xml version="1.0" encoding="UTF-8"?><phpunit bootstrap="tests/bootstrap.php" colors="true" verbose="true"> <testsuites> <testsuite name="Unit"> <directory>tests/unit</directory> </testsuite> <testsuite name="Integration"> <directory>tests/integration</directory> </testsuite> </testsuites>
<coverage processUncoveredFiles="true"> <include> <directory suffix=".php">class</directory> </include> <report> <html outputDirectory="coverage"/> </report> </coverage></phpunit>Skrive enhedstests
Sektion kaldt “Skrive enhedstests”<?phpnamespace Xoops\Module\Mymodule\Tests\Unit;
use PHPUnit\Framework\TestCase;use Xoops\Module\Mymodule\Service\UserService;
class UserServiceTest extends TestCase{ private $userService; private $mockRepository;
protected function setUp(): void { parent::setUp(); $this->mockRepository = $this->createMock( \Xoops\Module\Mymodule\Repository\UserRepositoryInterface::class ); $this->userService = new UserService($this->mockRepository); }
public function testRegisterSuccess() { // Arrange $this->mockRepository->expects($this->once()) ->method('findByUsername') ->willReturn(null);
$this->mockRepository->expects($this->once()) ->method('save') ->willReturn(1);
// Act $result = $this->userService->register('user', 'test@test.com', 'pass');
// Assert $this->assertNotNull($result); }
public function testRegisterDuplicate() { // Arrange $existingUser = new \stdClass(); $this->mockRepository->expects($this->once()) ->method('findByUsername') ->willReturn($existingUser);
// Act & Assert $this->expectException(\Exception::class); $this->userService->register('user', 'test@test.com', 'pass'); }}?>Test af dataobjekter
Sektion kaldt “Test af dataobjekter”<?phpclass UserDTOTest extends TestCase{ public function testDTOCreation() { $user = new User(); $user->setId(1) ->setUsername('testuser') ->setEmail('test@test.com');
$dto = new UserDTO($user);
$this->assertEquals(1, $dto->getId()); $this->assertEquals('testuser', $dto->getUsername()); }
public function testDTOToArray() { $user = new User(); $user->setId(1)->setUsername('testuser');
$dto = new UserDTO($user); $array = $dto->toArray();
$this->assertIsArray($array); $this->assertEquals(1, $array['id']); }}?>Kodedækning
Sektion kaldt “Kodedækning”# Generate coverage report./vendor/bin/phpunit --coverage-html coverage
# View coverage percentage./vendor/bin/phpunit --coverage-textBedste praksis
Sektion kaldt “Bedste praksis”- Skriv en test pr. metode/scenarie
- Brug beskrivende testnavne
- Følg Arrange-Act-Assert-mønsteret
- Håne ydre afhængigheder
- Hold testen fokuseret og uafhængig
- Sigt efter 80%+ kodedækning
- Test fejltilstande
- Test grænsetilfælde
Testorganisation
Sektion kaldt “Testorganisation”tests/├── unit/│ ├── UserServiceTest.php│ ├── UserRepositoryTest.php│ └── UserDTOTest.php├── integration/│ ├── UserControllerTest.php│ └── UserServiceTest.php├── fixtures/│ └── users.php├── bootstrap.php└── phpunit.xmlRelateret dokumentation
Sektion kaldt “Relateret dokumentation”Se også:
- Fejlhåndtering til undtagelsestest
- ../Patterns/Repository-Pattern til repository test
- ../Patterns/Service-Layer til servicetest
- Kode-Organisation for teststruktur
Tags: #best-practices #testing #phpunit #code-coverage #module-development