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

05.

Behat Hooks Background

|

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 Chapter

Login or register to check out the script

13 Comments

Sort By

Login or Register to join the conversation

Fancy name thingy 5 years ago edited

You should really put some quotes around that realpath call, I got far too close to accidentally wiping something important because I have spaces in my path

rm: cannot remove 'C:\Users\MyFirstName': No such file or directory
rm: cannot remove 'MyLastName\Google': No such file or directory
rm: cannot remove 'Drive\Pro': No such file or directory
rm: cannot remove 'Testing\2.': No such file or directory
rm: cannot remove 'BDD,': No such file or directory
rm: cannot remove 'Behat,': No such file or directory
rm: cannot remove 'Mink': No such file or directory
rm: cannot remove 'etc\test_temp': No such file or directory```



Luckily none of those existed as directories


So not `system('rm -r '.realpath('test_temp'));` but `system('rm -r "'.realpath('test_temp').'"');`

|

MolloKhan SFCASTS Fancy name thingy 5 years ago

Thanks for your input on that. I agree with you, it's safer to do that, and as a reminder, do not run scripts as sudo :)

Cheers!

|

Florian 8 years ago

Hey,
do you know why

//Works
if (is_dir('test')){
system('rm -r '.realpath('test'));
}

works but

//Don't work
if (is_dir('test')){
system('rm -r'.realpath('test'));
}

not? The difference is, there is a space between -r and '. Works -> 'rm -r ' | Don't work 'rm -r' This is strange.

|

weaverryan SFCASTS Florian 8 years ago edited

Hi Florian!

Ah, it's because system() ultimately runs a command-line script. If you think about it, the two commands would be:


rm -r /path/to/test

rm -r/path/to/test

If there's no space, the -r flag "runs into" the path :).

Cheers!

|

Phil 8 years ago

Not sure where is the best place to ask this - maybe here?
I am using @insulated tag for scenarios that run mink-selenium tests on SauceLabs, and SauceLabs creates a separate set of screenshots/video for each scenario. I have code that gets the URL of the SauceLabs job output and can write that to the log in the @AfterScenario - all good, I can look in the log for the inidividual link to the SauceLabs output for each scenario.
I can also send the pass-fail status of the scenario to SauceLabs (they have an API for that).
Is there some way, inside an AfterScenario method, to get the pass/fail status of the scenario?

|

Phil Phil 8 years ago

I just needed to look - scenario scopes have getTestResult which has isPassed()

/**
* After Scenario. Report the pass/fail status.
*
* @return void
* @AfterScenario
*/
public function reportResult(\Behat\Behat\Hook\Scope\AfterScenarioScope $afterScenarioScope) {
if ($afterScenarioScope->getTestResult()->isPassed()) {
$passOrFail = "pass";
$passed = "true";
} else {
$passOrFail = "fail";
$passed = "false";
}

$jobId = $this->getSessionId();
$sauceUsername = getenv('SAUCE_USERNAME');
$sauceAccessKey = getenv('SAUCE_ACCESS_KEY');

if ($sauceUsername && $sauceAccessKey) {
error_log("SAUCELABS RESULT: ($passOrFail) https://saucelabs.com/jobs/...");
exec('curl -X PUT -s -d "{\"passed\": ' . $passed . '}" -u ' . $sauceUsername . ':' . $sauceAccessKey . ' https://saucelabs.com/rest/... . $jobId);
}
}

|

weaverryan SFCASTS Phil 8 years ago edited

Haha, awesome - thanks for sharing the solution Phil! :)

|

Daniel Noyola 8 years ago

is there a way to use the "use" sentence and avoid the "include_once"? it just feels ugly. what I should add to the featureContext class if I want to test an API using Guzzle?

|

weaverryan SFCASTS Daniel Noyola 8 years ago

Hey Daniel!

Inside FeatureContext, you *do* have access to any of your normal classes (e.g. anything in the vendor directory, etc). So, you should be able to use Guzzle without needing any require statements - and actually, we do this in the REST tutorial (http://knpuniversity.com/sc... or https://github.com/knpunive... to see usage - though this is an older version of Guzzle now).

We added the require_once in this case to get the PHPUnit *functions* - as function autoloading is a bit different. However, this may not be needed anymore even for functions - I believe PHPUnit takes care of autoloading these automatically now as well.

I hope that helps!

P.S. Sorry for the slow reply!

|

Daniel Noyola weaverryan 8 years ago

Cool! this is getting more amazing!

P.S. it's okay as long you were working on this https://events.drupal.org/n... or this https://events.drupal.org/n...

|

weaverryan SFCASTS Daniel Noyola 8 years ago

Haha, let's say I was ;). Will you be there?

|

Daniel Noyola weaverryan 8 years ago

Yes! First DrupalCon ever :)

|

weaverryan SFCASTS Daniel Noyola 8 years ago

Awesome! DrupalCon is one of my absolute favorite conferences - incredibly well-run and great people. See you there!

|

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 Chapter