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

11.

Mocking: Stubs

|

|

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

14 Comments

Sort By

Login or Register to join the conversation

ahmedbhs 1 year ago

If the project involves developing a RESTful API and we plan to make requests to our own API, it would be ideal to have functional tests with fake fixtures, or having unit tests (using mocks), or both types of tests.

|

Victor SFCASTS ahmedbhs 1 year ago edited

Hey @ahmedbhs ,

Yeah, agree! Actually, no matter if you're gonna make requests to your own API or it will be only your users - those tests would be good to have. It mostly may depend on the specific API (project) and how complex that is.

Cheers!

|

Yacintosh 2 years ago edited

Hello, thanks for this course. Can you explain why tests are accepted with wrong title and label?

$mockResponse->method('toArray')->willReturn([
            [
                'title' => 'Daisy',
                'labels' => [
                    ['name' => 'Status: Sick'],
                ],
            ],
            [
                'title' => 'BadXxxx',
                'labels' => [
                    ['name' => 'Status: WrongTest'],
                ],
            ],
        ]);

|

sadikoff Yacintosh 2 years ago edited

Hello @Yacintosh

At this moment we do not test if data is correct, you will see it in the next chapters and there will be a test to cover this situation

Cheers!

|

lid 2 years ago

A very nice course.

One Point: A Service-Class should be stateless per definition. Symfony's HTTP-Client is stateful. When storing it in a class-member, the whole service-class isn't stateless anymore.

|

MolloKhan SFCASTS lid 2 years ago edited

Hey @lid

Good point, but I don't think it's a problem as long as your service class serves only one API, because as far as I know, the HTTP client only holds configuration, so you can reuse that object to perform different HTTP requests to the same API

Cheers!

|

Felipe-L 2 years ago

Hi,

great tutorial so far, quite enjoyable.
I've got a question related to testing response from real service.
In this case, we won't call github api because we don't control it and our test fails if it's unavailable, for example.
Mocking the Response will make sure tests are going to pass but the application won't have the correct status.
For example, the API is unavailable or changed its array structure, tests will pass but I'll never find out the application is broke (it won't be able to get health status from github).
My question is: is there a way to test the scenario?

thanks

|

MolloKhan SFCASTS Felipe-L 2 years ago edited

Hey @Felipe-L

In that case, you'd have to make a real API call to GitHub. I don't see a value in doing a health check of the API on your tests because that's outside of your control, it's better to have a retry mechanism or the ability to tolerate failures (disable the feature on the frontend)

Cheers!

|

Felipe-L MolloKhan 2 years ago

Hi @MolloKhan, thanks for your reply.
I got what you said and agree that's not on our control to test an API call.
Lets say my application depends on this feature to work properly. Would be a good idea to mark the test as skipped if it's not possible to return the content from the API?
Then have another mechanism to let us know that the API is unavailable?

thanks

|

MolloKhan SFCASTS Felipe-L 2 years ago

I think we're talking about two things.
1) Testing a real API response to be aware of changes. In this case, your test will need to make a real request to the API, that's sometimes fine, but keep in mind that those tests are slow, so you want to have just a handful of them
2) API health status. You can add a test where you mock out the response, and it will always return an error so you can test how your application behaves in that circumstance. For example, you could show a warning message on the frontend
Also, as I said earlier you can add a retry mechanism. This can be easily integrated with Symfony Messenger

Cheers!

|

Tac-Tacelosky 3 years ago

What's up with all the !!!!!!?

use.....!!!!!!!!!!!!!!!!!!! And, for the test, we'll pretend she sprained her ankle so add a labels key set to an array, that includes 'name' => 'Status: Sick'

!!!!!!!!!! Zoom back to the Github Issues to "circling" Maverick!!!!!!!!!!!!!!!!!!! Let's also cr...

|

Victor SFCASTS Tac-Tacelosky 3 years ago

Hey Tac!

Whoops, those are some dev comments we used when had been creating this tutorial. I fixed it in https://github.com/SymfonyCasts/testing/commit/2248a2b70b0fad08f2077271d6c3f4d7829d2473 , thank you for reporting it :)

Cheers!

|

Mario Victor 3 years ago edited

There is another instance of this.
!!!!!!!!! This chapter is short enough, we could? run the tests !!!!!!!!!
around 1:22 min of the video

|

weaverryan SFCASTS Mario 3 years ago

Ah! The script was fixed, but the subtitles need to be regenerated. We'll get on that! Thanks for the note :)

|

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