Thread:Manual talk:Coding conventions/Cucumber/How to document custom setup


 *  At the moment we tag features or scenarios that are known to fail on a clean wiki with @needs-custom-setup.

How do I communicate what a feature needs? E.g. the collapse Flow feature test only works if there are topics on the page to collapse, likewise edit_existing requires an existing post on the page. Some needs are met by running other tests first, and others require manual set up, e.g. creating a "Selenium_user" account.

Some Flow features have a sentence "Assumes the test page has content... /It requires the cldr extension..." after the  line, but then in Sauce Labs' Test Session Details pages (example), this runs into the feature name in an h2 header:
 * Edit existing title Assumes that the test Flow page has at least two topics (with posts).: Edit existing post Flow-en.wikipedia.beta.wmflabs.org-linux-firefox#192