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 2: | Line 2: | ||
<h2>Template</h2> | <h2>Template</h2> | ||
Copy and paste into your text editor and remember to save in the right directory and as a .feature file | |||
<pre> | <pre> |
Revision as of 11:37, 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
@javascript @core Feature: In order to As an So I can Scenario: Given And When And Then
Template for when you have 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