Chapters

29 Chapters | 2:54:09 |

01

PHPUnit: Secure the Park

5:43
02

Tests, Assertions & Coding

6:40
03

TDD & Unit, Integration & Functional Tests

3:41
04

TDD in Practice

4:59
05

Factory Testing

7:03
06

Hooks: setUp, tearDown & Skipping Tests

4:53
07

Data Providers!

8:01
08

Coding, Adding Features, Refactoring

7:48
09

Handling Object Dependencies

6:46
10

Testing Exceptions

4:32
11

Exceptions Part 2: Adding Fence Security

7:11
12

Refactoring & Dependency Injection

6:16
13

Mocks & Test Doubles

5:18
14

Mocks: Control the Return Value

4:58
15

Mocks: expects() Assert Method is Called Correctly

4:13
16

Full Mock Example

7:21
17

Full Mock Example: the Sequel

3:57
18

Mocking with Prophecy

6:57
19

The Important CLI Options & phpunit.xml.dist

5:07
20

Integration Tests

9:18
21

Clearing the Database

6:19
22

Partial Mocking

3:59
23

Functional Tests

7:00
24

DomCrawler: Epic Beast of the Night

4:47
25

Test Fixtures & Fast Databases!

7:18
26

Loading Fixtures References

5:00
27

Testing a Form Submit

5:56
28

Continuous Integration: Activate the Robots

7:56
29

CircleCI Artifacts

5:13

This tutorial has a new version, check it out!

> PHPUnit (Legacy): Testing with a Bite

Buy Access to Course

14.

Mocks: Control the Return Value

|

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 Chapter

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

12 Comments

Sort By

Login or Register to join the conversation

Don W. 4 years ago edited

Hi,
I'm using Symfony 5 to follow along with this series.
I created a DinosaurFactory and using it like this in DinosaurFactoryTest


$dinosaur = DinosaurFactory::new([
            'length' => 1,
            'genus' => 'Velociraptor',
            'isCarnivorous' => TRUE,
        ])
            ->withoutPersisting()
            ->create()
            ->object();

I added following code in setUp method


$this->lengthDeterminator = $this->createMock(DinosaurLengthDeterminator::class);
self::getContainer()->set(DinosaurLengthDeterminator::class, $this->lengthDeterminator);

But the following doesn't work inside testItGrowsADinosaurFromASpecification


$this->lengthDeterminator->method('getLengthFromSpecification')
            ->willReturn(20);

I also created a services_test.yaml and made the service public


services:
    App\Service\DinosaurLengthDeterminator:
        public: true

I'm not sure if Factory can be used like that for this scenario. Could you please suggest how to inject mock dependency

|

MolloKhan SFCASTS Don W. 4 years ago

Hey Jack,

Why are you injecting the mocked class into Symfony's container? Are you in a functional test? In this case, you only need to instantiate the DinosaurFactory manually in your tests and pass the mocked DinosaurLengthDeterminator object as an argument

Cheers!

|

Don W. MolloKhan 4 years ago

oh okay. So I can't use the "DinosaurFactory::" and do "new DinosaurFactory()" with the mock service as an argument.
Thank you for the help

|

Don W. Don W. 4 years ago

No errors are thrown btw. Just the tests are failing as the return value is random, not 20. So I assume the main service is loaded instead of the mock.

|

Francois 4 years ago

Hello, and thanks a lot for this tutorial

I am confused with: "Instead of simply testing the return value of the method, we're testing how the code is written internally... which in some ways, we should not care about: that's the business of the function. All we are supposed to care about is the return value. Writing stricter tests take more time, and will break accidentally more often."

Can you precise?

Or I can :)
"Instead of simply testing the return value of the method, we're
testing how the code is written internally..."
But I feel that with $this->assertSame(20, $dinosaur->getLength()); we are testing the return value here, the $dinosaur, don't we?

"which in some ways, we should not care about: that's the business of the function."
You mean the tested function, growFromSpecification, right?

Thanks!

|

Victor SFCASTS Francois 4 years ago

Hey Francois,

As always, it depends :) Sometimes you can just make sure that the return value is exactly like we expected, but sometimes we need to make sure that the code internally works exactly as we want, for example, if we test user creation method, it should return a new User with some specified fields, but it also should send an email to the user. So, in this case we want to check the return value, but also make sure that the code inside of this method that sends the email was called, something like this. Agree, it requires more time to write those tests, it also may break more often, but that's the price to make sure that the internal code works properly too :)

I hope this helps!

Cheers!

|

Francois Victor 4 years ago

Thank you Victor

Thanks for this general explanation, which is useful, but I was more concerned about the specific case which is mentionned in this video :

Here, in this specific example, I can only see a test of the return value, but the speaker says "Instead of simply testing the return value of the method, we're testing how the code is written internally".

This is what I don't understand, I can only see the test of a return result in these lines:

$dinosaur = $this->factory->growFromSpecification($spec);
$this->assertSame(20, $dinosaur->getLength())

What do I understand wrong?
Thanks

|

Victor SFCASTS Francois 4 years ago

Hey Francois,

I believe in this spot the author means that's we're testing how the growFromSpecification() method works internally, i.e. with that asset that checks the return value we're making sure that the growFromSpecification() method created a proper object - it's happen internally in that method, and so we're kind of testing it internally subsequently, something like this. It's not only related to "$this->assertSame(20, $dinosaur->getLength());" but also to the above line as well: "$this->assertSame($expectedIsCarnivorous, $dinosaur->isCarnivorous(), 'Diets do not match');" - both are testing the result of the growFromSpecification() work, i.e. technically how it internally works.

I hope this helps!

Cheers!

|

Francois Victor 4 years ago

Hum yes ok, I guess this exemple is a bit "in the middle", but I get the point anyway.
Thanks a lot!

|

triemli 5 years ago edited

Guys Can I ask you?
I created a mock of object


$userStub = $this->createMock(User::class);

Set it on return value of repository class:


$userRepositoryMock = $this->createMock(UserRepository::class);
$userRepositoryMock->method('getUserById')->willReturn($userStub);

Then I create a handler and execute it:


        $handler = new \Reset\Handler($userRepositoryMock);

        $handler->handle();

        self::assertEquals($userStub->geUsername(), 'John doe');

Inside of handler i get the user and use username setter! :


    public function handle(): void
    {
       /*here i must get a mocked user*/
       $user = $this->users->getUserById(10);

       /* change the same*/
       $user->setUsername('John doe'');
}

But assertion don't pass. It still empty. How to check it then?
Thanks

|

Victor SFCASTS triemli 5 years ago edited

Hey Sergei,

Because you mocked the User object - the method was called but it do nothing. PHPUnit just checked that the method you called is exist and that's it. First of all, usually, devs do not mock data objects like User in your case. Data objects are simple enough, so you can easily create real objects instead. Instead "$userStub = $this->createMock(User::class);" do "$user = new User();" and then change $userStub to $user further in the code and try again - it should work this way.

Or, if you want to continue using mocks for data objects, that I'd not recommend in this case, you can assert that "setUsername()" method was called once on that $userStub mocked object and that the argument passed was "John doe", e.g.:


$userStub->expects($this->once())
            ->method('setUsername')
            ->with('John doe')

Something like this.

Though your code inside handle() looks weird, as you're setting "John doe" username to every user? Is it ok? :)

Anyway, I hope this helps!

Cheers!

|

triemli Victor 5 years ago

Thanks for the answer. It's ok. Just for example made it simple. But yeah looks weird xD

|

While the fundamentals of PHPUnit haven't changed, this tutorial *is* built on an older version of Symfony and PHPUnit.

Symfony 3 PHPUnit 6

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.0, <7.4",
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/doctrine-bundle": "^1.6", // 1.10.3
        "doctrine/orm": "^2.5", // v2.7.2
        "incenteev/composer-parameter-handler": "^2.0", // v2.1.2
        "sensio/distribution-bundle": "^5.0.19", // v5.0.21
        "sensio/framework-extra-bundle": "^3.0.2", // v3.0.28
        "symfony/monolog-bundle": "^3.1.0", // v3.1.2
        "symfony/polyfill-apcu": "^1.0", // v1.6.0
        "symfony/swiftmailer-bundle": "^2.3.10", // v2.6.7
        "symfony/symfony": "3.3.*", // v3.3.13
        "twig/twig": "^1.0||^2.0" // v2.4.4
    },
    "require-dev": {
        "doctrine/data-fixtures": "^1.3", // 1.3.3
        "doctrine/doctrine-fixtures-bundle": "^2.3", // v2.4.1
        "liip/functional-test-bundle": "^1.8", // 1.8.0
        "phpunit/phpunit": "^6.3", // 6.5.2
        "sensio/generator-bundle": "^3.0", // v3.1.6
        "symfony/phpunit-bridge": "^3.0" // v3.4.30
    }
}

Previous Chapter

Next Chapter