Actions

Testing Area/Behat Testing/Characteristics of a good test: Difference between revisions

From Mahara Wiki

< Testing Area‎ | Behat Testing
No edit summary
No edit summary
Line 5: Line 5:
Copy and paste into your text editor and remember to save in the right directory and as a .feature file
Copy and paste into your text editor and remember to save in the right directory and as a .feature file


'''Single''' scenarios on a page
'''Single''' scenario on a page
<pre>
<pre>
  @javascript @core
  @javascript @core
Line 22: Line 22:


</pre>  
</pre>  
'''
'''Multiple''' scenarios on one page.
Multiple''' scenarios on one page.


<pre>
<pre>

Revision as of 11:39, 16 December 2014

How to write a good test

Template

Copy and paste into your text editor and remember to save in the right directory and as a .feature file

Single scenario on a page

 @javascript @core
 Feature: 
  In order to 
  As an
  So I can

 Scenario:
  Given
  And
  When
  And
  Then 


Multiple scenarios on one page.

 @javascript @core 
 Feature: 
  In order to 
  As an
  So I can

 Background:
  Given
  And
  And
  And  

 @core_
 Scenario:
  Given
  And
  When
  And
  Then 

 @core_
 Scenario:
  Given
  And
  When
  And
  Then


Feature

Good features clearly explain what you are trying to do. If you are using a bug from Launchpad to write the test, use the title of the bug in the title of the feature.

Feature:
 In order to 
 As a
 So I can 


Tags

Always attach a @javascript tag

Scenario


Background


Steps


Comments