Update "I should see a :label field" methods for Drupal 8

[becw]

• Updates the "BeforeScenario" and "AfterScenario" hooks so that they don't throw unnecessary exceptions
• I tested the "I should see a :label field" tests work under Drupal 8
• I also tested the markup tests under Drupal 8, which mostly work (one does not yet, so I've left an exception in there)

Also, re: #29, I updated the README -- turns out, the contexts added to behat.yml shouldn't have the .php extension :)

To test this, you can go into your project's vendor/palantirnet/palantir-behat-extension and check out this branch, then run tests like:

  Scenario: This should pass for a plain Drupal install
    Given I am logged in as an "administrator"
    When I visit "node/add/page"
    Then I should see a "Body" field
    And I should not see a "Nonexistent" field

  Scenario: This should fail for a plain Drupal install because the field doesn't exist
    Given I am logged in as an "administrator"
    When I visit "node/add/page"
    Then I should see a "Nonexistent" field

  Scenario: This should fail for a plain Drupal install because the field exists
    Given I am logged in as an "administrator"
    When I visit "node/add/page"
    Then I should not see a "Body" field

[labbydev]

@becw even after adding the extension in composer

        {
            "type": "vcs",
            "url": "[email protected]:palantirnet/palantir-behat-extension.git"
        }

and re-running composer install I'm not see vendor/palantirnet/palantir-behat-extension. Is there something I'm missing?

[becw]

@labbydev did you also add it to the dependencies section of your composer.json?

[cpatrone]

@labbydev , @becw
Having the repository defined as you have in your composer.json file and running from the command line "composer require palantirnet/palantir-behat-extension:dev-drupal8 --dev" should install the D8 branch of the extension (adding in require-dev section in composer.json the corresponding line). Please Beck correct me if I'm wrong ...

[zendoodles]

@labbydev @becw Don't we prefer https over the ssh? I forget why, but I remember running into trouble with the git@ version of these.

        {
            "type": "vcs",
            "url": "https://github.com/palantirnet/palantir-behat-extension.git"
        }

So... with ^ that in your composer.json, to add it to the require-dev section of composer.json so you can test this branch you would run

composer require palantirnet/palantir-behat-extension:dev-before-after-notupdated-exceptions --dev

(Note the branch is not drupal8. It is this branch.)

[labbydev]

@becw This works great except that these two extensions conflict with one another:

Drupal\DrupalExtension\Context\MarkupContext::assertRegionButton()
Palantirnet\PalantirBehatExtension\Context\MarkupContext::assertRegionButton()

[labbydev]

We should remove this rule from our Markup Context so that it fixes the duplication:

Step "I should see the button :button in the :region( region)" is already defined in Drupal\DrupalExtension\Context\MarkupContext::assertRegionButton()

Or we should add directions to just use our Markup Context instead of the Drupal one. But either way it should be addressed.

[becw]

@zendoodles I haven't had those problems with https vs git protocols recently, and it seems like it's working for @cpatrone as well; however, if it's still an issue, perhaps you can submit a patch to the README?

[becw]

We don't have the line in our markup context; our markup context extends the other markup context, and then the way that our behat.yml is set up means that it is like... instantiated twice (one Drupal\DrupalExtension\Context\MarkupContext and one Palantirnet\PalantirBehatExtension\Context\MarkupContext). So I guess we need to make instructions not to have both in the behat.yml for a project.

[labbydev]

@becw I added this information as Issue #32 I think this PR should be good to merge.

(I'm considering the issue temporary documentation until we have time to update the README)