13

Is it possible to reuse a feature as the "Given" for another feature?

Or am I trying to do something I shouldn't be trying to do

basically my features look like:

Scenario: Creating a basic account with valid details (happy path)
  Given I am on the "signup" page
  And I enter all the right details #this is shortened of about 20 steps for your reading ease
  When I press the button labelled "Sign up"
  Then I should see the text "Thanks for signing up"
  And I should have an email from "confirmation@mysite.com" titled "Confirm your account Michael"
  And the database should contain a record for the user marked as unconfirmed

Scenario: Confirming account via email
  Given I have created a basic account
  When I open the confirmation email and visit the url to confirm the account
  Then I should be logged in
  And the database should contain a record for the user makred as confirmed

I clear my DB after every feature as they should all be able to be run individually...

Am I going about this the wrong way?

Thanks

cjapes
  • 99
  • 9
Michael Baldry
  • 1,990
  • 2
  • 14
  • 28
  • Possible duplicate: http://stackoverflow.com/questions/7646696/how-to-use-common-shared-blocks-between-cucumber-features – Jon M May 30 '12 at 11:58
  • @JonM Good link on the related question. However, while the answers ended up being similar, I think the questions are slightly divergent. The question you reference is about sharing blocks, while this one is about calling features from features--something that Cucumber used to explicitly support, but no longer does. – Todd A. Jacobs May 31 '12 at 07:10

3 Answers3

13

The Problem

What you're actually attempting is to reuse a scenario. This is no longer supported in Cucumber.

Aside from other problems with this approach, your tests will be slower and interdependent, since you will be:

  1. driving account creation through a browser, and
  2. making all your tests dependent on the account-creation test passing.

Don't do that.

The Cucumber Way

Generally, you should write your tests to work independently, although you can certainly reuse step definitions. So, in the general case, you might want to add shared steps like:

  1. Given that user account "Test User" does not exist
  2. Given that user account "Test User" exists

which can then be included in your scenarios as needed. The nice thing about this approach is that the steps can create or delete users programmatically.

Alternatively, if most of your tests will be on existing accounts, set up the default data set with the right user fixtures already in place. For the limited subset where you will be testing account creation, just add a scenario background that drives user deletion.

Todd A. Jacobs
  • 81,402
  • 15
  • 141
  • 199
1

In case you are using Javascript, I've created a package named reuse-cucumber-scenarios for calling a scenario by doing:

Given the scenario "@scenario_tag"

.

Given the scenario "@scenario_tag" with parameters
"""
{
  "1": ["step1_param1", "step1_param2"],
  "2": ["step2_param1", "step2_param2", "step2_param3"],
  "3": ["step3_param1", "step3_param2", "step3_param3"],
}
"""

or creating gherkin variables...

Given the variable "$variable_name" is equal to
"""
#JSON object
"""

or creating scenario functions and calling them by doing...

Given the scenario "@$scenario_function_tag" where variable "$variable_name" is "value_to_replace"

and more...

Virgomax
  • 11
  • 1
  • 2
0

Currently, you can use the following approach:

Background:
  Given Some common setup
  And Some more setup

Scenario: one
  When setup1
  Then something1

Scenario: two 
  When setup2
  Then something2
miro
  • 131
  • 2
  • 9