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

15.

Mocks: expects() Assert Method is Called Correctly

|

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

4 Comments

Sort By

Login or Register to join the conversation

Mehul-J 4 years ago

It was nice if you would have showed the testing of eventsubscribers and eventlisteners

|

weaverryan SFCASTS Mehul-J 4 years ago edited

Hey Mehul-J!

That's actually a good point! I test these with 2 strategies:

1) Unit test: if the code is complex enough, I'll unit test the event listener method. But usually, if the logic is this complex, I'll isolate the main part of the logic to a separate class and unit test *that* class.

2) Functional test: Once your logic is unit tested (somewhere), all you really need to know is "is my event listener/subscriber" correctly configured so that it was executed? Depending on what your listener does, this can be tricky or not tricky. Basically, I would make a request (in a test) to my site in order to trigger the event listener, and then "assert" something that it did.

I noticed that you asked this in the "mocks" section, so I may not have answered exactly what you were asking - let me know if that's the case :). If I were unit testing an event listener/subscriber, I would mock any constructor dependencies it has... but for the event argument, I would typically try to create that directly, as those are usually simple objects. But if it's complicated enough, you could mock that too.

Cheers!

|

Matt 7 years ago

Wrong code block after line **Awesome! Move back to DinosaurFactory, and re-fix the length line. Double-check that this fixes things. It does!**

|

MolloKhan SFCASTS Matt 7 years ago

@Matt Thanks for informing us! I just fixed that code block :)

|

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