Chapters

16 Chapters | 1:17:50 |

01

Instalación de PHPUnit

4:01
02

Nuestra primera prueba

7:16
03

Probar los métodos de la clase

6:57
04

TDD - Desarrollo dirigido por pruebas

4:19
05

TDD Parte 2: Terminar y refactorizar

4:37
06

Proveedores de datos

4:28
07

Pruebas incompletas y dinos bailarines

6:26
08

Crea una prueba de servicio en GitHub

4:29
09

Servicio GitHub: Implementación

4:47
10

Burlas: Dobles de prueba

6:07
11

Mocking: Stubs

4:01
12

La burla: Objetos simulados

4:27
13

Filtrar los dinos hambrientos

3:45
14

Probando Excepciones Excepcionales

4:01
15

Simular el cliente Http de Symfony

2:49
16

Configuración y desmontaje

5:20

> Testing > PHPUnit: ¡Pruebas Unitarias con un Bocado!

Buy Access to Course

14.

Probando Excepciones Excepcionales

|

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $10.00

Previous Challenge

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

4 Comments

Sort By

Login or Register to join the conversation

yaroslavche 3 years ago

Since we're using PHP ^8.0, I think that also correct way to use null-coalesce operator throwing an exception:

return HealthStatus::tryFrom($status) ?? throw new \RuntimeException(sprintf('%s is an unknown status label!', $status));

In that case, we don't need to declare extra variables, but should think about line length and good readability.
Also, in case within two issues for same Dinosaur with different labels we can face exception, when shouldn't (if latest label is Healthy, but previous is unknown and not closed for some reasons).

In addition, in test class it's possible to instantiate an exception, and use expectExceptionObject, which can be useful in some cases (f.i., within data providers).

|

weaverryan SFCASTS yaroslavche 3 years ago

Hi yaroslavche!

That's a cool idea to use the null-coalesce to throw an exception - like it!

In addition, in test class it's possible to instantiate an exception, and use expectExceptionObject()

I'm actually not familiar with expectExceptionObject() - and I could find almost no info on it! It looks undocumented, though a comment on StackOverflow says that it works as of PHPUnit 9.5. So, super interesting!

Cheers!

|

yaroslavche weaverryan 3 years ago

expectExceptionObject is just a sugar for expectException, expectExpceptionMessage and expectExceptionCode.

$this->expectException(\RuntimeException::class);
$this->expectExceptionMessage('Drowsy is an unknown status label!');
$this->expectExceptionCode(1);

the same as

$this->expectExceptionObject(new \RuntimeException('Drowsy is an unknown status label!', 1));

|

weaverryan SFCASTS yaroslavche 3 years ago

Beautiful - I like that a lot!

|

PHPUnit 9 Symfony 6.1

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.1.0",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "symfony/asset": "6.1.*", // v6.1.0
        "symfony/console": "6.1.*", // v6.1.4
        "symfony/dotenv": "6.1.*", // v6.1.0
        "symfony/flex": "^2", // v2.2.3
        "symfony/framework-bundle": "6.1.*", // v6.1.4
        "symfony/http-client": "6.1.*", // v6.1.4
        "symfony/runtime": "6.1.*", // v6.1.3
        "symfony/twig-bundle": "6.1.*", // v6.1.1
        "symfony/yaml": "6.1.*" // v6.1.4
    },
    "require-dev": {
        "phpunit/phpunit": "^9.5", // 9.5.23
        "symfony/browser-kit": "6.1.*", // v6.1.3
        "symfony/css-selector": "6.1.*", // v6.1.3
        "symfony/phpunit-bridge": "^6.1" // v6.1.3
    }
}

Previous Challenge

Next Chapter