This mirrors my own experiences using Gherkin syntax in other tech stacks. The most workable scenario I've come up with is to focus on simple, terse syntax that

This mirrors my own experiences using Gherkin syntax in other tech stacks. The most workable scenario I've come up with is to focus on simple, terse syntax that is still readable. Build reusable page objects, keep your actual tests short and things get nice and easy. Lots of good options in this space. A few years ago I built FluentAutomation [1] to solve this issue in the .NET community. [1] http://fluent.stirno.com/ http://fluent.stirno.com/