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

04.

Behat

|

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 Challenge

Next Challenge

Login or register to check out the script

8 Comments

Sort By

Login or Register to join the conversation

ahmadmayahi 7 years ago edited

I think it's much better to implement a ls command by using the DirectoryIterator class than to use the shell_exec() to run the unix ls.

|

weaverryan SFCASTS ahmadmayahi 7 years ago edited

Hey ahmadmayahi!

Yea, I'd agree actually :). This is just an example, and the point is to actually test the ls command itself. But if I really wanted directory info in PHP, I'd totally not do it this way. Actually, I usually use Symfony's Finder component - it's got a few extra nice features.

Cheers!

|

Muhammad Taqi Hassan 8 years ago

You show that we can see how many steps are passed and failed. Is there any quick way to know which step is failed and detail reason for that?

|

weaverryan SFCASTS Muhammad Taqi Hassan 8 years ago

Hey Muhammad!

Yes! Well, probably :). The Behat executable has a number of different output options, so that the final output can be more or less descriptive. By default, it summarizes (at the bottom) how many steps passed/failed, and you can scroll up to see which steps fails with the detailed reason (well, semi-detailed: Behat only knows which *step* failed, and the error message that was thrown that caused the failure). By using the the --format (or just -f) flag, you can change the output: http://docs.behat.org/en/v2...

Alternatively, you could use a hook to do some custom logging on each failure - see https://knpuniversity.com/s...

Let me know if that helps!

Cheers!

|

lindsay macvean 8 years ago

Im pretty sure that the ls command would have been developed by the fathers of Unix at Bell laboratories back in the 70s :) FWIW

|

weaverryan SFCASTS lindsay macvean 8 years ago

Ah damn, that is almost definitely true :).

|

AJ 8 years ago

This comment is for the previous "Challenge 2 of 2" (https://knpuniversity.com/s... there is a quote (") missing after "Given there is a" in the Scenario box.

|

weaverryan SFCASTS AJ 8 years ago

Thanks AJ! I got that quote added now!

|

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 Challenge

Next Challenge