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

18.

Mocking with Prophecy

|

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

26 Comments

Sort By

Login or Register to join the conversation

Radoje Albijanic 8 years ago edited

Hey folks!

If you installed symfony/phpunit-bridge like suggested in the first video, you will have to install prophecy too, I didn't have prophecy classes until run:


composer require phpspec/prophecy

Cheers.

14 |

weaverryan SFCASTS Radoje Albijanic 6 years ago edited

Hi!

Just an update on this old problem :). First, sorry for anyone who it it - we should have added a clear note much earlier. Second, the reason that you don't have Prophecy when you use symfony/phpunit-bridge is that it specifically removes it. It does that for some historical reasons that aren't important. But, you can tell the phpunit-bridge that you do want Prophecy by adding one line to your phpunit.xml.dist file:


&lt;!-- phpunit.xml.dist --&gt;
&lt;!-- ... --&gt;

    &lt;php&gt;
         &lt;!-- ... --&gt;
         &lt;env name="SYMFONY_PHPUNIT_REMOVE" value="symfony/yaml" /&gt;
    &lt;/php&gt;

If you do this, you should not need to install phpspec/prophecy directly in your app: it will be included normally when the phpunit-bridge downloads phpunit.

Cheers!

2 |

MolloKhan SFCASTS Radoje Albijanic 8 years ago edited

Hey Radoje Albijanic

Thanks for informing us about it. We will add a note, so no one else get confused :)

Cheers!

|

Nils L. MolloKhan 6 years ago edited

MolloKhan No note in the video ... :)

1 |

sadikoff Nils L. 6 years ago edited

Hey Nils L.

Can you provide some more info about why it needed? Are you running phpunit directly? or vie Symfony's PHPUnit bridge? Which version of PHPUnit do you have?

Cheers!

|

Nils L. sadikoff 6 years ago

sure .. as recommended i use symfony's PHPUnit Bridge "symfony/phpunit-bridge": "^4.0.5".
that installed "phpunit/phpunit": "^7.5"

|

Mepcuk 4 years ago

Hi,
FYI - incorrect video filename

|

sadikoff Mepcuk 4 years ago

Forget :) we already checked it! Thanks for the reporting!

Cheers!

|

sadikoff Mepcuk 4 years ago edited

Hello Mepcuk

Give me please more details what is wrong with it?

Cheers!

|

Gonzalo G. 5 years ago edited

Hello there , a question, how would the test of a method like the one I show below be approached:

public function execute(array $terms_array): array {
$items = [];
$base_uri = $this->getSetting('base_url');
foreach ($terms_array as $term_item) {
$items[] = $this->getPeople($term_item, $base_uri);
}
return array_merge([], ...$items);
}

Any suggestions on how it would be done?

|

MolloKhan SFCASTS Gonzalo G. 5 years ago edited

Hey Gonzalo G.

I think I'd test only the state of what it returns instead of the algorithm because it calls a few other methods. I'd pass an input that I already know what the output should be and assert that

Cheers!

|

Todor 6 years ago edited

Somehow my PhpStorm doesn't fully autocomplete the Prophecy part.

It works:

<br />$this->prophesize(...);<br />

It doesn't works:

`
// 1) Argument remains as an undefinied class
// 2) shouldBeCalledTimes is not found too

$em->persist(Argument::type(...))->shouldBeCalledTimes(...)
`

My Setup is as follows:

PHP 7.4.5
PhpStorm 2020.1.2
PHPUnit 8.3
PHP Toolbox 5.1.1
PHPUnit Enhancement 4.1

Anything special you have to do for prophecy support? It isn't working out of the box for me.

Update: well it seems that I don't have the Prophecy classes at all.
$this->prophesize(...); throws Class 'Prophecy\Prophet' not found.
Since I am using the course code with phpunit-bridge. and that points out again to the very first comment from Radoje Albijanic about the missing note.
After two years the note is still missing :D

Well though when I try to add prophecy manually
composer require phpspec/prophecy

I get a bunch of dependencies conflicts.

Cheers!

|

weaverryan SFCASTS Todor 6 years ago edited

Hey Todor!

Yikes! We have a system in place to get notes added to tutorials, but we somehow dropped the ball on this one! My apologies for the trouble :/. As Vladimir mentioned, this could be a PHP 7.4 problem, or it could be something else. If you want to post the dependency error conflict, we can help manager it.

In the mean time, we'll get the note added (we need to play with the code a bit first to make sure we get the note just right).

Cheers!

|

weaverryan SFCASTS weaverryan 6 years ago edited

Hi again weaverryan!

After my research, I've found the problem (and the correct note to add). You should not need to install prophecy manually. That may work, but phpunit already comes with prophecy. The reason that you do not see it is that, when simple-phpunit installs PHPUnit, it removes Prophecy from the install. It does this for some historical reasons related to dependencies. But if you do want prophecy, you can enable it via your phpunit.xml.dist file:


&lt;!-- phpunit.xml.dist --&gt;
&lt;!-- ... --&gt;

    &lt;php&gt;
         &lt;!-- ... --&gt;
         &lt;env name="SYMFONY_PHPUNIT_REMOVE" value="symfony/yaml" /&gt;
    &lt;/php&gt;

That tells the phpunit-bridge that it's ok to remove symfony/yaml (something it does in older versions) but it should not remove prophecy. Try that and let us know how it works!

Cheers!

|

sadikoff Todor 6 years ago edited

Hey Todor

This course is a little bit old and it doesn't support php 7.4. you can see this requirement in composer.json file. We are trying to improve code delivery to be more strict you can see a tooltip on "Download > Courser code" dropdown menu, but yeah it's just a text tooltip and composer still allows installation.

BTW Course code works great on php 7.3 ;) However we can't guarantee that it will work if you update packages to latest version. As I can see you are using PHPUnit 8, but course is based on PHPUnit 6 there can be a lot of differences in code but main principles of testing are same.

Cheers!

|

oleksii_khromets 6 years ago edited

Why there are so many errors in this course?
After 2 years, did you find that you have an error code in the last example in this video?
`
$em->persist(Argument::type(Enclosure::class)

    ->shouldBeCalledTimes(1);


$dinoFactory 
	    ->growFromSpecification(Argument::type('string')
	    ->shouldBeCalledTimes(2)
	    ->willReturn(new Dinosaur());
`
Where is the closing parenthesis (after Argument definition)?

|

sadikoff oleksii_khromets 6 years ago edited

Hey alexchromets

Good catch, interesting how it happend :( however we just fixed this code block, so keep eye and feel free to report such cases!

Cheers!

1 |

_zippp 6 years ago

seems like the libraries used in the tutorial a bit dated, for those who's got "Prophecy" classes not found error you need to add it to your project vendors:
composer require phpspec/prophecy

|

weaverryan SFCASTS _zippp 6 years ago edited

Hey _zippp !

Sorry for the slow reply! We were checking into this. Prophecy comes with PHPUnit automatically... so it's interesting that your app was missing them. What version of PHPUnit are you using ./vendor/bin/phpunit --version? And are you using PHPUnit directly (i.e. you run it via ./vendor/bin/phpunit) or are you using it via Symfony's PHPUnit bridge (i.e. you run it with php bin/phpunit)? Let us know - I'd love to add a note to the tutorial if we need one!

Cheers!

|

Marcel D. 7 years ago

There is a typo in subtitles at 0:58 second. It should be use $em = $this->prophesize(EntityManagerInterface::class) instead of use $this->em->prophesize(EntityManagerInterface::class).

|

MolloKhan SFCASTS Marcel D. 7 years ago edited

Hey Marcel D.

Thanks for informing us about it. We really care about our quality :)

Cheers!

1 |

Matt 7 years ago edited

Found two typos:

Missing closing bracket in`
$em->persist(Argument::type(Enclosure::class)`

Missing closing bracket in`
->growFromSpecification(Argument::type('string')`

|

MolloKhan SFCASTS Matt 7 years ago

Fixed now!

|

weaverryan SFCASTS Matt 7 years ago

Hey @Matt!

Nice catch! We're going to update those ASAP! Thanks for letting us know!

Cheers!

|

toporovvv 8 years ago

There are two typos here:
$this->em->prophesize(EntityManagerInterface::class) - em is redundant here.

And here closing bracket was missed:
$em->persist(Argument::type(Enclosure::class)
->shouldBeCalledTimes(1);

|

MolloKhan SFCASTS toporovvv 8 years ago edited

Thanks toporovvv!
I just fixed it :)

1 |

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