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 1: | Line 1: | ||
<h1>How to write a good test</h1> | |||
<h2>Feature</h2> | <h2>Feature</h2> | ||
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 | |||
<h2>Tags</h2> | <h2>Tags</h2> | ||
Always attach a @javascript tag | |||
<h2>Scenario</h2> | <h2>Scenario</h2> |
Revision as of 11:20, 16 December 2014
How to write a good test
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