Scenarios

We've created our features, which is really nice because we can see the
business value of each and decide which one to start on first. I want to
start with our product admin feature, so our admin users can start loading
in data.

Now that we've selected that, we'll start adding scenarios to the feature which
are essentially user stories. My first scenario is going to say, "when I go to
the admin area and click on products, I see the products listed."

For these scenarios I need you to think as if you are the admin user. We'll talk in
the first person point of view at the intended user's technical level. Meaning, clicking
on buttons an admin user can actually recognize and viewing things that they will
see. Put yourself in their shoes.

Scenarios always have three parts, the first is Given where you can create any type of
setup before the user story starts. So in our case, if we want to list products, we need
to make there are some in the database to see:

In Given you can add things to the database before hand, but once you are in When and
Then you should only be taking actions that the admin user could take and viewing things
they can view. This means we won't be using CSS selectors in our scenarios or phrasing such
as "Then a product should be entered into the database" because a user can't see that happen.
However, the user could see a helpful message, like "Celebrate, your product was saved!"

And I fill in "Description" with "Have your velociraptor chew on this instead!"

... lines 18 - 20

There is a secret reason of why I'm using language like "I fill in" after the And,
which we'll cover soon. Lastly, in our process I'll expect to hit a save button to
finish creating my new product. So let's add another line to our scenario: