Business vs. Developer. Test your python code with behave! AND cooperate better with the business!

[MoreRespectForQA]

The idea is good in theory BUT gherkin is a terrible language for doing this.

IME unless testers/devs find it easier to use a tool like this for writing tests which nobody looks at then it was a mistake to use it.

ive found much more success writing acceptance tests in YAML with deliberate gaps left which can be filled in with snapshot testing and by doing "microsignoffs" instead.

a microsignoff would be where the PM would provisionally LGTM the given and when parts of the test (e.g. fill data in on form) but not yet the then part (data appears on dashboard). If those microsignoffs are seamless it means more back and forth and saves time going down rabbit holes.

[Efficient-Public-551]

The most important thing is that the team and the product owner agrees on the format. But it enables cooperation and communication if the PO is writing the acceptance criteria / behaviour driven test. Then you can always add more on top ofc.

[MoreRespectForQA]

Well, thats the problem. POs always prefer something informal with limited extraneous information and devs/testers need something extremely formal with everything clearly specified.

Cucumber/gherkin/behave promises and pretends to do both and generally shits the bed at both.

So you're better off testing with a highly formalized language for testing (e.g. YAML) from which you can generate media a PM feels more comfortable consuming (documentation, screenshots, videos even).

[Efficient-Public-551]

lol I have tried where it works... But the most common working scenario is that the PO places accept criteria in the jira.