Cucumber for acceptance testing

[pburls]

Summary

Cucumber is a test framework for running acceptance test captured in Gherkin syntax.

Opinion(s)

If the work intake process starts producing acceptance criteria for new work in the form of Gherkin syntax, it makes sense to maintain our acceptance test packs (edge to edge and end to end) using the Cucumber test framework.

We propose this goes into the Tools quadrant as it helps the shape the software that we develop.
For now it will go into the Trial ring of showing how this will work.

Teams interested in this tech

Currently being trialed by the Mercury team for acceptance testing.
Is used in some teams for their own integration tests, like Gonzales.

[pburls]

We should look at how this compares with our Groovy + Spock radar item under Languages & Frameworks quadrant.

[pburls]

Decision: More information about the appropriate time and place to use the framework should be included in the summary. Also some links to examples and best practice is needed.

[pburls]

To be assigned to Fouad Hussain from Mercury team.

[FHN06]

1. e2e skeleton being finalised
2. work intake process to be socialised with leadership (with Sumit)
3. grad team to start using cucumber to create gherkin journeys (product Owner role to support the development of the automation capability and the actual journeys cross sky)