Document Behat-gherkin step text

[phil-davis]

What Type Of Content Change Is This?

• New Content Addition
• Old Content Deprecation
• Existing Content Simplification
• Bug Fix to Existing Content

Which Manual Does This Relate To?

• Admin Manual
• Developer Manual
• User Manual

What Needs to be Documented?

The top part of the developer acceptance-tests.adoc describes the layout of the tests/acceptance folders and how to write new acceptance test features. It has got a long way out of date.

• Port Backport: Change integration to acceptance tests owncloud-archive/documentation#3870 to the docs repo.
• document the standard grammar forms that we are using to write Given When and Then step text Document how we write acceptance tests #398
• document the tags that we use Add section about tagging scenarios to acceptance-tests.adoc #624
• document what steps are available in core (probably just the really common ones that people will make use of a lot in writing new scenarios)
• give an overview of other steps that are available, and how to search for, find and use
• give guidelines for how to write the code for new API acceptance test steps How to add new acceptance test steps #650
• give guidelines for how to write the code for new CLI acceptance test steps How to add new acceptance test steps #650 (nothing special here that is in principle different to API tests)
• give guidelines for how to write the code for new webUI acceptance test steps
• give guidelines on what makes a "good" test scenario Document how we write acceptance tests #398
• how to write scenarios for bugs (ref: Documenting existing behavior when bugs are found QA#601 ) Writing Scenarios For Bugs #633

Why Should This Change Be Made?

Developers (and managers/designers/end users?) need a reference to help them write good and standardized acceptance tests.

[phil-davis]

Issue transferred and updated from the original issue in owncloud-archive/documentation#3829

Also see discussion in owncloud/QA#517