brunty/laravel-behat-fixtures

This package is abandoned and no longer maintained. No replacement package was suggested.

Provides a way to load fixture data into the DB when using Behat with Laravel

0.2 2017-03-25 20:55 UTC

Requires

• behat/behat: ^3.3
• behat/mink: ^1.7
• behat/mink-extension: ^2.2
• illuminate/support: ^5.4
• laracasts/behat-laravel-extension: ^1.0

MIT

• Matt Brunt

README

Installation

This package requires that you have the Laracasts: Behat Laravel Extension setup and working. Due to relying on that to load and setup Laravel for us.

composer require brunty/laravel-behat-fixtures --dev

Configuration

Include the fixture in your suite, and pass it the path to your fixtures folder:

default:
    suites:
        default:
            contexts:
                - Brunty\LaravelBehatFixtures\FixtureContext:
                    - '%paths.base%/features/bootstrap/fixtures/'

Usage

Resetting & Refreshing the Database

This package gives access to a tag that uses the BeforeScenario hook. It refreshes your database migrations before each scenario, use @db-refresh either before every scenario in a feature, or individual scenarios:

# Will be called before each scenario in the feature
@db-refresh
Feature: My amazing feature

  # Will be called before only scenarios tagged with this
  @db-refresh
  Scenario: Things
    Given nothing is happening
    When nothing happens
    Then nothing should have happened

Fixtures

Creating files within the fixture folder enables them to be loaded into features and scenarios. These are just plain ol' PHP files, so you can create things using Laravel's factory() method, or using Eloquent methods on your Models:

%paths.base%/features/bootstrap/fixtures/users.base.php

<?php

// Create users via factories
$users = factory(App\User::class, 5)->create();

// Alternatively, you can just do whatever you'd like with eloquent
$user = new \App\User(['name' => 'Matt', 'email' => '[e-mail]', 'password' => bcrypt('apassword')]);
$user->save();

You can then load these fixture files with the @fixture tag, where the tag content is the fixture file name (minus the .php extension):

@db-refresh
Feature:

  @fixture(users.base)
  Scenario: Things
    Given nothing is happening
    When nothing happens
    Then nothing should have happened

If you wanted to load multiple fixtures for a scenario, you can do so:

@db-refresh
Feature:

  @fixture(users.base) @fixture(users.active)
  Scenario: Things
    Given nothing is happening
    When nothing happens
    Then nothing should have happened

These would then be loaded in the order: users.base.php followed by users.active.php

Contributing

This started as a project of boredom one Saturday evening, if you find yourself using this, and want more features, please feel free to suggest them, or submit a PR!

Although this project is small, openness and inclusivity are taken seriously. To that end the following code of conduct has been adopted.

Contributor Code of Conduct