Chapters

39 Chapters | 4:45:13 |

01

Hello API Security + API Docs on Production?

8:55
02

API Auth 101: Session? Cookies? Tokens?

4:05
03

Login with json_login

6:27
04

Authentication Errors

5:55
05

Login Success & the Session

4:28
06

On Authentication Success

7:40
07

Logout & Passing API Data to JS on Page Load

8:49
08

SameSite Cookies & CSRF Attacks

8:06
09

ApiResource access_control

6:03
10

Bootstrapping a Test Suite

4:29
11

Backport the API Platform 2.5 Test Tools

5:01
12

Api Tests & Assertions

6:51
13

Logging in Inside the Test

6:57
14

Resetting the Database Between Tests

4:51
15

Base Test Class full of Goodies

8:30
16

ACL: Only Owners can PUT a CheeseListing

9:23
17

ACL & previousObject

8:04
18

Access Control & Voters

8:25
19

Adding the plainPassword Field

7:31
20

Data Persister: Encoding the Plain Password

8:03
21

Validation Groups

5:44
22

Conditional Field Setup

6:42
23

Testing, Updating Roles & Refreshing Data

9:22
24

Context Builder & Service Decoration

6:50
25

Context Builder: Dynamic Fields/Groups

7:47
26

Automatic Serialization Groups

5:59
27

Resource Metadata Factory: Dynamic ApiResource Options

8:45
28

Dynamic Groups without Caching

10:34
29

Custom Normalizer: Object-by-Object Dynamic Fields

9:30
30

Diving into the Normalizer Internals

4:49
31

A "Normalizer Aware" Normalizer

6:49
32

Normalizer & Completely Custom Fields

7:32
33

Locking down the CheeseListing.owner Field

8:16
34

Custom Validator

5:40
35

Security Logic in the Validator

6:46
36

Auto-set the Owner: Entity Listener

9:46
37

Query Extension: Auto-Filter a Collection

9:37
38

Automatic 404 on Unpublished Items

5:26
39

Filtering Related Collections

10:50

This tutorial has a new version, check it out!

> Symfony 5 > API Platform 2 Part 2: Security

Buy Access to Course

22.

Conditional Field Setup

|

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 $12.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

CISVHenriksen 6 years ago

data-start-time="339.276" -> does not work? (testGetUser)

I get a failure stating: Symfony\Component\HttpClient\Exception\JsonException: Response content-type is "text/html; charset=UTF-8" while a JSON-compatible one was expected.

api-platform/core v2.5.5
symfony/http-client v4.3.11
symfony/http-foundation v4.3.11
symfony/http-kernel v4.3.11
symfony/phpunit-bridge v5.0.8

|

CISVHenriksen CISVHenriksen 6 years ago

Well well well, Dumb Typo! 🙃 had the line: "$client->request('GET', '/api/users/'.$user->getId());" wrong. forgot trailing / on users 😁

|

Sung L. 6 years ago

Is it possible to run test without running fixtures?

I have installed AliceBundle and created fixtures to generate sample data. However, whenever I run test, fixtures load automatically. Especially when I use `ReloadDatabaseTrait`, fixtures run every test cases. I can use `RefreshDatabaseTrait ` to run only once per resource test, but I was wondering if we can run test without running fixtures.

Any tips? Thanks!

|

sadikoff Sung L. 6 years ago edited

Hey Sung L.

Of course you can, but it depends on what are you testing. Without fixtures you will need to think more about data that you are testing, how not to get errors about duplicated data, or probably some more

Cheers! Hope this will help.

|

Sung L. sadikoff 6 years ago edited

Hi sadikoff

So..how can I run test without running fixtures? I want to keep fixtures because it helps to generate contents, but I don't want to regenerate fixtures everytime I run test. :)

|

sadikoff Sung L. 6 years ago

Ok, lets begin from start, you want to run course code, and course tests, but without regenerating fixtures everytime, am I right?

|

Sung L. sadikoff 6 years ago

Yes, that's correct. I like the tests shown in this video tutorial, create a new user, updating, and so on. But I'd like to see the front end filled with fixture data when I need to working on frontend UI.

Let's say I have 500 fixture data for ChesseListing. Every time I run the test, it regenerate 500 cheeses which is overkill. I would like to skip this step, regenerating data, ONLY when I run testing. Or if there is a flag in `./bin/phpunit --skip-fixture` for example, that would be perfect!

|

sadikoff Sung L. 6 years ago edited

Hey Sung L.

Sorry for so late answer, it was crazy SymfonyCon week :) So I understand you point of view! Hm you can try to use separate DB for test environment without fixtures, and fully control data inside your tests

Cheers!

|

This tutorial works great for Symfony 5 and API Platform 2.5/2.6.

Symfony 4 API Platform 2.4

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3, <8.0",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "api-platform/core": "^2.1", // v2.4.5
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // 1.13.2
        "doctrine/doctrine-bundle": "^1.6", // 1.11.2
        "doctrine/doctrine-migrations-bundle": "^2.0", // v2.0.0
        "doctrine/orm": "^2.4.5", // v2.7.2
        "nelmio/cors-bundle": "^1.5", // 1.5.6
        "nesbot/carbon": "^2.17", // 2.21.3
        "phpdocumentor/reflection-docblock": "^3.0 || ^4.0", // 4.3.1
        "symfony/asset": "4.3.*", // v4.3.2
        "symfony/console": "4.3.*", // v4.3.2
        "symfony/dotenv": "4.3.*", // v4.3.2
        "symfony/expression-language": "4.3.*", // v4.3.2
        "symfony/flex": "^1.1", // v1.21.6
        "symfony/framework-bundle": "4.3.*", // v4.3.2
        "symfony/http-client": "4.3.*", // v4.3.3
        "symfony/monolog-bundle": "^3.4", // v3.4.0
        "symfony/security-bundle": "4.3.*", // v4.3.2
        "symfony/twig-bundle": "4.3.*", // v4.3.2
        "symfony/validator": "4.3.*", // v4.3.2
        "symfony/webpack-encore-bundle": "^1.6", // v1.6.2
        "symfony/yaml": "4.3.*" // v4.3.2
    },
    "require-dev": {
        "hautelook/alice-bundle": "^2.5", // 2.7.3
        "symfony/browser-kit": "4.3.*", // v4.3.3
        "symfony/css-selector": "4.3.*", // v4.3.3
        "symfony/maker-bundle": "^1.11", // v1.12.0
        "symfony/phpunit-bridge": "^4.3", // v4.3.3
        "symfony/stopwatch": "4.3.*", // v4.3.2
        "symfony/web-profiler-bundle": "4.3.*" // v4.3.2
    }
}

Previous Chapter

Next Chapter