Cucumber tests (and acceptance tests in general) are similar to the tests we've been writing in the rest of the book. They are focused on specifying examples of behavior. They should be specific in nature: they should not talk in abstract terms, but make use of real data and numbers as a means to test a general concept, just as we've done in the two examples in this chapter. All this is in common with unit tests.
The essential difference from our unit tests is that acceptance tests are done at a much higher level. You don't need to test every single detail in your features, unlike in your unit tests, which will get all the details ironed out.
Just as with unit tests, it's important to find ways to simplify the code. The number one rule is to try to write generic Given, When, and Then phrases that can be reused across classes and extracted out of step...
