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

23.

Tagging Scenarios in order to Load Fixtures

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 Course

Remember way back in the beginning when we had search feature? Try running that again:

./vendor/bin/behat features/web/search.feature

Huh, this one is failing now: it says that the text "Samsung Galaxy" was not found anywhere on the page. Now that you're an expert, I hope you can spot the problem: we're not adding this product at the beginning of the scenario. This worked originally because the fixtures that come with the project have a "Samsung Galaxy" product. But now that other tests have cleared the database, we're in trouble.

We could put some Given statements at the top to add the products. But there's another way: load the project's fixtures automatically before the scenario. This LoadFixtures class is responsible for putting in the Kindle and Samsung products.

I think that entering the data manually with the Given statements is the most readable way to do things. But, if you do load the fixtures, here's the best way. First, I don't want to load fixtures before every scenario. That would make my scenarios run slower, even when I don't need that stuff.

Tagging Scenarios

Instead, I need a way to tag scenarios to say "this one needs fixtures". Add @fixtures at the top of this scenario outline:

            Copy Code

                            Show All Lines

                        19 lines
            |
            features/web/search.feature
        
            Feature: Search
        
              In order to find products dinosaurs love
        
              As a website user
        
              I need to be able to search for products
        
                Show Lines

                                                    // ... lines 6 - 8
                            
              @fixtures
        
              Scenario Outline: Search for a product
        
                Show Lines

                                                    // ... lines 11 - 19

That's called a tag, and you can put many as you want, separating each by a space. At first, adding a tag does nothing except for the magic @javascript that changes to use a JavaScript driver.

Running things Before a Tagged Scenario

But in FeatureContext you can add an @BeforeScenario method that's only executed when a scenario has a certain tag. Make a new public function loadFixtures(). Inside, just to see if it's working, put var_dump('GO!');. Above, put the normal @BeforeScenario:

            Copy Code

                            Show All Lines

                        258 lines
            |
            features/bootstrap/FeatureContext.php
        
                Show Lines

                                                    // ... lines 1 - 42
                            
                /**
        
                 * @BeforeScenario @fixtures
        
                 */
        
                public function loadFixtures()
        
                {
        
                    var_dump('GO!');
        
                }
        
                Show Lines

                                                    // ... lines 50 - 258

Here's the trick: after this, add @fixtures. Now, this will only run for scenarios tagged with @fixtures. To prove that, re-run our search.feature:

./vendor/bin/behat features/web/search.feature

There's our 'GO!'. Now run the authentication.feature:

./vendor/bin/behat features/web/authentication.feature

This passes with no var_dump(). Perfect!

Loading the Fixtures

One way to execute the fixture is by running the doctrine:fixtures:load command. I use a different method that gives me more control. Add $loader = new ContainerAwareLoader() and pass it the container:

            Copy Code

                            Show All Lines

                        263 lines
            |
            features/bootstrap/FeatureContext.php
        
                Show Lines

                                                    // ... lines 1 - 47
                            
                public function loadFixtures()
        
                {
        
                    $loader = new ContainerAwareLoader($this->getContainer());
        
                Show Lines

                                                    // ... lines 51 - 53
                            
                }
        
                Show Lines

                                                    // ... lines 55 - 263

Now, point to the exact fixtures objects that you want to load. There are two methods available: loadFromDirectory() or loadFromFile(). Move up a few directories and load from src/AppBundle/DataFixtures:

            Copy Code

                            Show All Lines

                        263 lines
            |
            features/bootstrap/FeatureContext.php
        
                Show Lines

                                                    // ... lines 1 - 50
                            
                    $loader->loadFromDirectory(__DIR__.'/../../src/AppBundle/DataFixtures');
        
                Show Lines

                                                    // ... lines 52 - 263

That should do it!

Next, create an $executor = new ORMExecutor() and pass it the entity manager:

            Copy Code

                            Show All Lines

                        263 lines
            |
            features/bootstrap/FeatureContext.php
        
                Show Lines

                                                    // ... lines 1 - 51
                            
                    $executor = new ORMExecutor($this->getEntityManager());
        
                Show Lines

                                                    // ... lines 53 - 263

A purger is the second argument, which you only need if you want to clear out data. We're already doing that, so I'm not going to worry about it here. Finally type $executor->execute($loader->getFixtures()) and pass true as the second argument:

            Copy Code

                            Show All Lines

                        263 lines
            |
            features/bootstrap/FeatureContext.php
        
                Show Lines

                                                    // ... lines 1 - 52
                            
                    $executor->execute($loader->getFixtures(), true);
        
                Show Lines

                                                    // ... lines 54 - 263

This says to not delete the data, but to append it instead.

Ok, run search.feature:

./vendor/bin/behat features/web/search.feature

It fails for a completely different reason. Things are never boring here! This is a unique constraint violation because it's not clearing out the data before loading the fixtures. This is a funny edge case. Because the new @BeforeScenario is near the top and the other for clearing the data is lower, they're being run in that order. Move these @BeforeScenarios up top and keep them in the order that you want:

            Copy Code

                            Show All Lines

                        263 lines
            |
            features/bootstrap/FeatureContext.php
        
                Show Lines

                                                    // ... lines 1 - 35
                            
                /**
        
                 * @BeforeScenario
        
                 */
        
                public function clearData()
        
                {
        
                    $purger = new ORMPurger($this->getContainer()->get('doctrine')->getManager());
        
                    $purger->purge();
        
                }
        
                /**
        
                 * @BeforeScenario @fixtures
        
                 */
        
                public function loadFixtures()
        
                Show Lines

                                                    // ... lines 49 - 263

Back to the terminal and run this sucker again!

./vendor/bin/behat features/web/search.feature

Pop the champagne people, it passes! It clears the data and then loads the fixtures. And life is super awesome!

Running Tagged Scenarios

There's another benefit to tagging scenarios. But first, if you ever need some details about the behat executable, run it with a --help flag to get all the info:

./vendor/bin/behat --help

One of the options is tags:

Only execute the features or scenarios with these tags

Well that's sweet. So we could say: --tags=fixtures and it will only execute scenarios tagged with fixtures:

./vendor/bin/behat --tags=fixtures

Or, we can get real crazy and say that we want to run all scenarios except the ones tagged with @fixtures by using the handy ~ (tilde) character:

./vendor/bin/behat --tags=~fixtures

behat -vvv

One more tip! If something goes wrong, there's also a verbosity option that will show you the full stack trace. Just add -v:

./vendor/bin/behat --tags=~fixtures -v

Hey, that's all! Hop in there, celebrate behavior driven development, create beautiful tests and sleep better at night!

See ya next time!

11 Comments

Sort By

Soltan 5 years ago

How can i make run finish script? I just downloaded it but when I run cucumber authentication.feature file I have this error below:
@BeforeScenario # FeatureContext::clearData()
│
╳ An exception occured in driver: could not find driver (Doctrine\DBAL\Exception\DriverException)

So all steps are skipping.
How can I fix it?
Thank you in advance.

| Reply |

weaverryan SFCASTS Soltan 5 years ago edited

Hey Soltan!

When you go into that finish directory, make sure to also open the README.md file - it has some setup instructions that you need, including initializing the database. In this case, because the tutorial uses MySQL, I believe your error means that you don't have the mysql or PDO extension compiled into your PHP. That's what the "could not find driver" means. Make sure you have the php-pdo extension installed - here are some more details about that: https://stackoverflow.com/q...

Cheers!

1 | Reply |

boykodev 6 years ago

Great course!
It's a pity I can't get a certificate of achievement because some challenges are not working :(

Update: They are working now! :)

| Reply |

MolloKhan SFCASTS boykodev 6 years ago edited

Hey boykodev

I see you also reported that some challenges were not working, I just check it out and they are working well. Could you confirm this? Thanks :)

| Reply |

boykodev MolloKhan 6 years ago

Yes, they all work fine now.

1 | Reply |

MolloKhan SFCASTS boykodev 6 years ago

Awesome, thanks!

| Reply |

Josh Crawmer 6 years ago

I keep getting an error for "The text "Samsung Galaxy S II" was not found anywhere in the text of the current page."

Here is my code:

/**
* @BeforeScenario @fixtures
*/
public function loadFixtures()
{
$loader = new ContainerAwareLoader($this->getContainer());
$loader->loadFromDirectory(__DIR__.'/../../src/AppBundle/DataFixtures');
$executer = new OrmExecutor($this->getEntityManager());
$executer->execute($loader->getFixtures(), true);
}

Everything has gone good up till this point. Please help!

| Reply |

weaverryan SFCASTS Josh Crawmer 6 years ago

Yo Josh!

If everything worked up to this point, it must be something small! If you add a var_dump('hey!') to loadFixtures and run just this one Scenario Outline, is it called? Also, if you add a "And print last response" to the outline, what do you see? Does the page work? Are the products visible on the page?

It could be several things - use the debugging tools from earlier: I'm sure we'll find the issue. Nothing stands out to me - so you must be close.

Cheers!

| Reply |

Josh Crawmer weaverryan 6 years ago

Hey Ryan. The var_dump inside the loadFixtures works fine. I also added a "And print last response" and on the page it showed a "No products found message" and the table was empty. It looks like my Features are running fine. It just seems that the fixtures are not getting loaded, once the loadFixtures method is called. Here is my code if you can look over quick and see if I missed something. Thanks! https://github.com/joshcraw...

| Reply |

weaverryan SFCASTS Josh Crawmer 6 years ago

Hey Josh!

Yep, now I see the problem: move clearData() *above* loadFixtures() - we talk about this near the bottom of this section: https://knpuniversity.com/s.... For you, it's adding the fixtures, and then clearing everything. Hence, no results :). It's a tricky one.

Cheers!

| Reply |

Josh Crawmer weaverryan 6 years ago

This worked great. Thanks a lot. This is kind of a weird piece of code:

$executer = new ORMExecutor($this->getEntityManager());
$executer->execute($loader->getFixtures(), true);

If is supply a new ORMPurger($em) object as the second argument to ORMExecuter(), then suddenly $executer->execute won't run unless I change true to false as the second argument. I just find it a little weird that what you pass to the second method is dependent upon what you pass to the constructor. I dunno. Maybe I'm being weird. Thanks for everything!

| Reply |

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 Course

Tagging Scenarios in order to Load Fixtures

Share this awesome video!

Keep on Learning!

Tagging Scenarios

Running things Before a Tagged Scenario

Loading the Fixtures

Running Tagged Scenarios

behat -vvv

11 Comments

Delete comment?

What PHP libraries does this tutorial use?

	Feature: Search
	In order to find products dinosaurs love
	As a website user
	I need to be able to search for products

Show Lines	// ... lines 6 - 8
	@fixtures
	Scenario Outline: Search for a product
Show Lines	// ... lines 11 - 19

Show Lines	// ... lines 1 - 42
	/**
	* @BeforeScenario @fixtures
	*/
	public function loadFixtures()
	{
	var_dump('GO!');
	}
Show Lines	// ... lines 50 - 258

Show Lines	// ... lines 1 - 47
	public function loadFixtures()
	{
	$loader = new ContainerAwareLoader($this->getContainer());
Show Lines	// ... lines 51 - 53
	}
Show Lines	// ... lines 55 - 263

Show Lines	// ... lines 1 - 50
	$loader->loadFromDirectory(__DIR__.'/../../src/AppBundle/DataFixtures');
Show Lines	// ... lines 52 - 263

Show Lines	// ... lines 1 - 51
	$executor = new ORMExecutor($this->getEntityManager());
Show Lines	// ... lines 53 - 263

Show Lines	// ... lines 1 - 52
	$executor->execute($loader->getFixtures(), true);
Show Lines	// ... lines 54 - 263

Show Lines	// ... lines 1 - 35
	/**
	* @BeforeScenario
	*/
	public function clearData()
	{
	$purger = new ORMPurger($this->getContainer()->get('doctrine')->getManager());
	$purger->purge();
	}

	/**
	* @BeforeScenario @fixtures
	*/
	public function loadFixtures()
Show Lines	// ... lines 49 - 263