Given: that real-world scenarios are more complicated than examples
    And: sites are now bloated with many layers of components
   When: I write feature tests
   Then: I want them to be simple, abstract
    And: I want them to be thorough and precise

A set of utility methods, on top of behave test framework. This goes further than the Gherkin language, implementing a more rich set of operators and testing flows.

1. Standard web (browser) calls Binds to selenium in a consistent way
2. Inventory of web components Allows web elements to be referenced, discovered and grouped in a declarative way
3. Method steps Makes Gherkin scenarios re-usable through abstracting in a step
4. Test flows Implement branching and looping within Gherkin scenarios.

See: https://behave-manners.readthedocs.io/

Panos Christeas [email protected]

This repository is provided under a BSD license, and consists of personal work by the Author(s) as above. Unless explicitly noted and clearly marked, no other parties, no current or former employers of the Author(s) should be associated with this project nor its license.