Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Made some minor change to make it read more easily #566

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 10 additions & 12 deletions docs/intro/wtf.rst
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Since Lettuce is used to test the behavior of a project, the behavior is broken
up in to features of the system.

After enumerating features, you need to create scenarios which will
describe those feature. Thus, scenarios are components of a feature.
describe those features. Thus, scenarios are components of a feature.

Let's learn by example: suppose we want to create a system to manage an
address book.
Expand Down Expand Up @@ -110,8 +110,6 @@ Suppose that we need to fill the same form many times, each time
with a different data set. This is how it could be done using scenario
outlines:

Let's see how it could be done with scenario outlines:

::

Feature: Apply all my friends to attend a conference
Expand All @@ -133,8 +131,8 @@ Let's see how it could be done with scenario outlines:
| Lincoln | lincoln@provider.net | 1987/09/10 |
| Marcus | marcus@other.org | 1990/10/05 |

In a nutshell, the scenario above is equivalent to write the huge code
bellow
In a nutshell, the scenario above is equivalent to the huge code
bellow:

::

Expand Down Expand Up @@ -167,12 +165,12 @@ bellow
Fill the field "birthday" with "1990/10/05"
Click on "confirm attendance" button

As you can notice, scenario outlines are very useful and help you on
avoiding text and code repetition
As you will notice, scenario outlines are very useful and help you to
avoid text and code repetition.

*************************
Steps and its definitions
*************************
***************************
Steps and their definitions
***************************

Comparable with Scenarios, Steps comes in two kinds:

Expand All @@ -196,8 +194,8 @@ Tabular steps
Analog to Outlined Scenarios, the tabular steps are very useful, and
avoid repetition of text.

Tabular steps are specially useful to set up some data set in a
scenario, or to compare a set of data to the expected results in the
Tabular steps are especially useful to set up some data set in a
scenario, or to compare a set of data to the expected results at the
end of the scenario.

However, feel free to use this whenever you find it useful.
Expand Down