title: Best BDD practices for designing Cucumber scenarios for forms
body: <p>Lets say you have a form which creates a new user.
  How do you write your Cucumber scenario?</p>
  
  <p>1.)</p>
  
  <pre><code>Given I am logged in as admin
  When I create a new user
  Then I should see "Successfully created user"
  </code></pre>
  
  <p>2.)</p>
  
  <pre><code>Given I am logged in as admin
  When I go to Create new user
  And I fill in "Name" with "Name111"
  And I fill in "Password" with "Password111"
  And I press "Create new user"
  Then I should see "Successfully created user"
  </code></pre>
  
  <p>If you choose 1.) where do you document the requirements for a User (A user should have a name and a password). I see that BDD is about behavior but at some point you and the stakeholder have to specify which properties a user should have, don't you?</p>
  
  <p>I'm very new to BDD so I appreciate any advise...</p>