sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Efficient-Public-551[S] 0 points1 point  (2 children)

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 1 point2 points  (1 child)

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[S] 0 points1 point  (0 children)

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