Step library

BDD methodology don't concede you from using any steps description you want. But if you reuse steps you got valuable working time economy on unique step implementation. Step library contains most common test step and oriented on some simplified test workflow. According to this scenario should have following stucture

Scenario: Most common scenario
  Go to some page
  Find some element with text1
  Do something with found element
  Check if some attribute is some value
  ...

Steps

• Go to <url>
  To navigate to given url. Usually it used as configuration step in the beginning of scenario.

• Find <element> with <text>
  To find element containing text

• Click found item
  Make click on on element found on previous step.

• Check if <attribute> is <value>
  Stop if <attribute> is <value>
  To check some attributes of elements found on previous steps on equality/non-equality to given value. It sentence is started with Check then it just save state to log. Stop will break scenario execution and switch to next scenario. Instead of is can be is not, are, are not

• Switch to found item
  To reach elements inside other complex elements.

• Switch to frame <n>
  To change focus to the frame for access elements inside frames and iframes.

• Wait <n> seconds
  To wait n second before next step.

Forms

This group of step is used to fill forms.

• Enter <text>
  To enter text to text inputs found on previous steps.

Animation

This group of step is intended for creating guides.

• Say <text>
  To show text close to fake mouse pointer.

• Highlight and say <text>
  To highlight element found on previous step and add comment close to highlighted element.