Chapters

23 Chapters | 1:59:49 |

01

From Install to JS Testing

7:27
02

BDD Features

5:56
03

Scenarios

4:24
04

Behat

6:08
05

Behat Hooks Background

6:49
06

Mink

3:30
07

Finding Elements by CSS and Name

6:48
08

Behat Loves Mink (Free Definitions from MinkExtension)

2:56
09

Scenario Outline

2:10
10

Mink Session inside FeatureContext

6:00
11

Context Organization and Behat Suites

4:03
12

Building a Login Scenario

3:57
13

Controlling the Database

4:24
14

The SymfonyExtension & Clearing Data Between Scenarios

5:13
15

Practice: Find Elements, Login with 1 Step and Debug

6:51
16

When *I* do Something: Handling the Current User

4:10
17

Practicing BDD: Plan, then Build

8:09
18

Master JavaScript with Waits & Debugging

6:16
19

Debugging and Taking Screenshots with JavaScript

3:33
20

Gherkin Tables: Given I have the following:

4:37
21

Finding inside HTML Tables

2:20
22

Clicking a Row in a Table (i.e. Complex Selectors)

8:55
23

Tagging Scenarios in order to Load Fixtures

5:16

> Testing > BDD, Behat, Mink and other Wonderful Things

Buy Access to Course

02.

BDD Features

|

Autoplay

Previous Chapter

Next Challenge

Login or register to check out the script

10 Comments

Sort By

Login or Register to join the conversation

mehdi 8 years ago

Hi there,
Can you clarify the last paragraph from " it will focus our
efforts ....." ? I read it many times but I don't get it.
I understand that in "In order to" we put the feature description from the user perspective and in " I need to be able to" we put the feature description from the developer perspective.

|

weaverryan SFCASTS mehdi 8 years ago edited

Hey mehdi!

Of course :).

I understand that in "In order to" we put the feature description from the user perspective and in " I need to be able to" we put the feature description from the developer perspective.

Yes, this is quite a good way of explaining it! So, in the last paragraph, here is what I'm trying to say. If your In order to is written well, then it will really explain the purpose of this feature: why we are building it, and how the user of this feature will benefit. This is important, because, as developers, it helps us think about the purpose of this feature. So, when I go to build the production admin area, instead of "focusing" on making forms and adding buttons, I'll be thinking about the feature from the user's perspective.

Let me give you a real example. If I am not thinking about how the user will actually use our new product admin area, then I might (as a developer) add a lot of extra features that aren't needed - maybe a cool upload widget, or a super fancy text editor. But, if I think about what the admin user actually wants to accomplish, I may realize that some of these features are not actually necessary or even wanted. I might instead think of other ways to improve/build the admin area that will actually help them with their business value. So, it "focuses" us on building the admin area in the correct way: build it for the user.

I hope this helps!

Cheers!

|

AJ 8 years ago

Ah okay. This script is for the previous chapter's video and the previous chapter's script is for this video.

|

weaverryan SFCASTS AJ 8 years ago

You're right - the videos were flipped! I've fixed that at sha: https://github.com/knpunive...

Thanks!

|

boykodev 8 years ago

First challenge not working: "CodeMirror is not defined" in gherkin.js:25

|

MolloKhan SFCASTS boykodev 8 years ago edited

Hey boykodev!

Thanks for informing us about that sneaky bug, we will fix it as soon as possible

Cheers!

1 |

boykodev MolloKhan 7 years ago

Even after one year passed, it's still not working...:(
The message is different though, now it says:
"Your challenge machine shutdown! We do this after awhile for security reasons. Reload the page to get a fresh challenge."

|

boykodev boykodev 7 years ago

Same for challenges 3.1 and 5

|

GDIBass 8 years ago

Really liking the challenges in this one!

|

MolloKhan SFCASTS GDIBass 8 years ago

Cool, keep it going!

1 |

This tutorial uses a very old version of Symfony. The fundamentals of Behat are still valid, but integration with Symfony will be different.

Symfony 2 Behat 3

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.4.0, <7.3.0",
        "symfony/symfony": "^2.7", // v2.7.4
        "twig/twig": "^1.22", // v1.22.1
        "sensio/framework-extra-bundle": "^3.0", // v3.0.16
        "doctrine/doctrine-bundle": "^1.5", // v1.5.1
        "doctrine/orm": "^2.5", // v2.5.1
        "doctrine/doctrine-fixtures-bundle": "^2.2", // v2.2.1
        "behat/symfony2-extension": "^2.0" // v2.0.0
    },
    "require-dev": {
        "behat/mink-extension": "^2.0", // v2.0.1
        "behat/mink-goutte-driver": "^1.1", // v1.1.0
        "behat/mink-selenium2-driver": "^1.2", // v1.2.0
        "phpunit/phpunit": "^4.8" // 4.8.18
    }
}

Previous Chapter

Next Challenge