如何在黄瓜上写测试？

Question

This is my first test case with cucumber and I am having tough time to figure out one thing. So I already have a test which check user creation. I want to add more steps like on user create create account and create product and set some attributes to these objects.

Here is the user create feature file

@no-database-cleaner

Feature: Creating an user account
  In order to use Recdns portal
  I need to create an user account

  Scenario:  Successful user account creation
    Given the database contains no test data
    And I am on the homepage
    When I attempt to create the following user account:
      | email address        | password | confirm password |
      | abc@company1.com  | password | password         |
  # User is automatically logged in
    Then I should see "Welcome!" message on page
    And an ar_id is set for the user
    And
    When I click "Sign Out"
    Then I should see "Signed out"
    When I attempt to sign in with following user account:
      | email address         | password |
      | abc@company1.com   | password |
    Then I should see "Welcome!" message on page

  Scenario Outline:  Verify error message when user failed to sign in
    Given there is a user
    And I am on the homepage
    And I try to login with email "<email address>", password "<password>"
    Then I should see "<error message>" message on page

  Examples:
    | email address                        | password          | error message                        |
    | testuser@company1.com                | abc1234           | Invalid email or password            |
    | testuserdoesnotexist@company1.com    | password          | Invalid email or password            |

  Scenario Outline:  Verify error message when user failed to sign up
    Given I am on the homepage
    And I click "Sign Up"
    And I try to create user with email "<email address>", password "<password>", confirm password "<confirm password>"
    Then I should see "<error message>" message on page

  Examples:
    | email address       | password          | confirm password      | error message                        |
    | abc@company1.com | abc123            | abc123                | Email has already been taken         |
    | xyz@test         | abc123            | abc123                | Email is invalid                     |
    |                     | abc123            | abc123                | Email can't be blank                 |
    | abc@company1.com |                   | abc123                | Password can't be blank              |
    | abc@company1.com | abc123            |                       | Password doesn't match confirmation  |
    | abc@company1.com | abc1              | abc1                  | Password is too short                |

So where exactly I can add steps saying create account table and product table. Thanks

Answer 1

Is your 'create user account' method something that you need for each test to run? If so, I'd just create a helper that you can call before your scenario. ..something like @needs_new_account. One of the best parts about cucumber is the ability to reuse environments. You probably shouldn't create a new account for each scenario. Instead, have cucumber remember that it needs to keep that new account (ie., dont delete it) and reuse for the rest of your scenarios, if possible. Let me know if this helps. ..not quite sure I'm understanding your question completely.

Also, you don't need your extra "and" between "and" and "when"...Gherkin syntax treats And/When/Then the same.