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

10.

Testing Exceptions

|

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

8 Comments

Sort By

Login or Register to join the conversation

CloudCreators 4 years ago

dinosaurs is an array of dinosaur, first() does what?

is it checking only the first dinosaur in the array?

return count($this->dinosaurs) === 0 || $this->dinosaurs->first()->isCarnivorous() === $dinosaur->isCarnivorous();

|

Victor SFCASTS CloudCreators 4 years ago

Hey Shubham,

The "dinosaurs" property is a Doctrine's ArrayCollection... but yeah, you can think about it like about an array on steroids, and the first() method returns the first value of that array or null if the array is empty, that's why we check if the array is NOT null first with "count($this->dinosaurs) === 0" check, and then we're sure that the first() will return a Dinosaur entity on which we can call that isCarnivorous() method and do not worry it will fail with "Method was called on null" error :)

Cheers!

|

Marcel D. 7 years ago edited

Hi friends! For those who are using PHPUnit 8 the @expectedException annotation is deprecated.

`
PHPUnit 8.0.4 by Sebastian Bergmann and contributors.

.......W.IS........ 19 / 19 (100%)

Time: 77 ms, Memory: 4.00 MB

There was 1 warning:

1) Tests\AppBundle\Entity\EnclosureTest::testItDoesNotAllowToAddNonCarnivorousDinosaursToCarnivorousEnclosure
The @expectedException, @expectedExceptionCode, @expectedExceptionMessage, and @expectedExceptionMessageRegExp annotations are deprecated. They will be removed in PHPUnit 9. Refactor your test to use expectException(), expectExceptionCode(), expectExceptionMessage(), or expectExceptionMessageRegExp() instead.

WARNINGS!
Tests: 19, Assertions: 31, Warnings: 1, Skipped: 1, Incomplete: 1.
`

Bye!

|

weaverryan SFCASTS Marcel D. 7 years ago edited

Hey Marcel D.!

Thanks for posting! You're totally right - you should now use the pure PHP way of expecting exceptions (the first we show) - but not the annotations :).

Cheers!

2 |

Abelardo weaverryan 5 years ago

Hi there,

Then you should delete the section which tells us about annotations to avoid to be followed by us.

Cheers!

|

Victor SFCASTS Abelardo 5 years ago

Hey AbelardoLG,

Unfortunately, we cannot delete anything in released tutorials, but we will add a note to warn about it. Thank you!

Cheers!

|

Boran Alsaleh 8 years ago

Hallo ,

why we have to make sure adding $this->expectException(NotBuffetException::class); before our last code
$Enclosure->addDinosaur(new Dinosaur('Carn Dinasour',true));

thnx ,

|

MolloKhan SFCASTS Boran Alsaleh 8 years ago edited

Hey Boran Alsaleh

Because when you add an expected exception like that, PHPUnit will wrap within a try-catch block your test method, so if it throws, it will check if the thrown exception matches to the one you specified, otherwise, the execution would explode (because you know, the code throwed an exception and nobody catched it)

I hope it helps you understanding what's going on here :)

Cheers!

|

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