Behave manners
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.
- Standard web (browser) calls
Binds to
selenium
in a consistent way - Inventory of web components Allows web elements to be referenced, discovered and grouped in a declarative way
- Method steps Makes Gherkin scenarios re-usable through abstracting in a step
- Test flows Implement branching and looping within Gherkin scenarios.