Skip to content

adding info on PHPUnit and PHP setup #529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
error256 merged 1 commit into from
Sep 10, 2026
Merged

adding info on PHPUnit and PHP setup #529

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions content/languages/php/phpunit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,15 @@ tags:

# PHPUnit

All [PHPUnit](https://phpunit.readthedocs.io/) tests start with a subclass of `TestCase`. You can then add one or more test case methods to that class, each of which must be public and start with `test`. In Codewars' PHP versions 7.4+, PHPUnit requires the name of the test class to end with `Test`.
All [PHPUnit](https://phpunit.readthedocs.io/) tests start with a subclass of `TestCase`. You can then add one or more test case methods to that class, each of which must be public and start with `test`. In Codewars' PHP versions 7.4+, PHPUnit requires the name of the test class to end with `Test`. For the same versions, every PHP file (user code, tests, and preloaded if anything is in there) should have the opening tag `<?php`, and every test file should have the import `use PHPUnit\Framework\TestCase;`. The PHP runner will concatenate them if missing, but it is a legacy behavior that should not be relied on for new content.

## Basic Setup

### Solution

```php
<?php

function add(int $a, int $b): int {
return $a + $b;
}
Expand All @@ -22,11 +24,16 @@ function add(int $a, int $b): int {
### Tests

```php
<?php

use PHPUnit\Framework\TestCase;

class AddTest extends TestCase {
public function testAdd() {
$message = "for input a = 1, b = 2";
$expected = 3;
$actual = add(1, 2);
$this->assertSame($expected, $actual);
$this->assertSame($expected, $actual, $message);
}
}
```
Expand Down Expand Up @@ -66,6 +73,8 @@ $actual->bar = "42";
$this->assertSame($expected, $actual); // fails
```

This is because `=== / assertSame` between PHP objects will merely check if they point to the same object (reference equality). `== / assertEquals` between objects should still be avoided, because [its semantics](https://www.php.net/manual/en/language.oop5.object-comparison.php) are very surprising, and it compares object properties with loose comparison.

Here, using [`assertObjectsEqual`](https://phpunit.readthedocs.io/en/9.5/assertions.html#assertobjectequals), which calls a class' `equals(self $other): bool` method, might be a more appropriate approach.

### Float equality
Expand All @@ -77,8 +86,9 @@ $this->assertEqualsWithDelta(0.99, "1", 0.1); // passes
$this->assertEqualsWithDelta(99999, true, 0.1); // passes
```

Type-checking the arguments to `assertEqualsWithDelta` before calling it or implementing a custom delta assertion based on `assertTrue` may be a safer bet.
Type-checking the arguments to `assertEqualsWithDelta` before calling it (with `assertIsFloat`) or implementing a custom delta assertion based on `assertTrue` may be a safer bet.

Another suprising fact is that unlike most languages, PHP considers `1` and `1.0` not to be strictly equal, so `assertSame(1, 1.0)` will fail. If you want to allow them to be strictly equal, you might want to cast the user's answer, e.g. `if (is_int($actual)) $actual = (float)$actual`, or the other way around.

<!--
TODO: Finish this reference
Expand Down
Loading