Question

in this tutorial is proposed this file system:

XXXBundle
   |---Features
   |      |----FeaturesContext.php
   |---ProductCategoryRelation.feature  

where FeaturesContext.php is the file that stores the functions

//FeaturesContext.php
/**
 * Feature context.
 */
class FeatureContext extends BehatContext
{
  /**
   * @Given /I have a category "([^"]*)"/
   */
  public function iHaveACategory($name)
  {
      $category = new \Acme\DemoBundle\Entity\Category();
      $category->setName($name);
  ...  

And inside ProductCategoryRelation.feature is proposed to write the features and the scenarios:

Feature: Product Category Relationship
  In order to setup a valid catalog
  As a developer
  I need a working relationship

This being the feature, we now need the scenarios to be defined.

Scenario: A category contains a product
  Given I have a category "Underwear"
  ...

But if my app is growing up, how should refactor for example FeaturesContext.php?

Answer 1

You might use subcontexts to split step definitions into multiple context classes: http://docs.behat.org/guides/4.context.html#using-subcontexts