Add Gherkin to languages and frameworks

[TommasoLencioni]

• I've added a short description of the entry that
  clarifies what it does and why it's useful
• I've added links to the entry's documentation and/or
  website
• My frontmatter is correct, complete and follows the
  format specified in the README
• In case the entry is in the adopt category: I've
  added at least one reference to showcase the entry usage
  among our organization
• I've described at least one use case for the entry

[gunzip]

I'd insert at least link to some helpful resource.

[gunzip]

Is this IDPay specific or it's used also in other products?

[TommasoLencioni]

The linked repo is IDPay specific, being the only place where Gherkin is used by CSTAR team.
As far as i can tell Gherkin is also used in other products:
https://github.com/pagopa/pagopa-taxonomy
https://github.com/pagopa/pagopa-nodo-dei-pagamenti-test
https://github.com/pagopa/pagopa-fdr

[gunzip]

Can you expand a litttle bit? ie. when it is supposed to be used, in unit tests or integration tests as well?

[TommasoLencioni]

I expanded all the sections, please check them out and let me know, thank you! 😄

[gunzip]

The entry is well-composed. However, I have reservations about including it in the 'adopt' quadrant. This classification typically implies widespread use of the technology across different teams, which may not yet be the case yet. Let's see if someone between CODEOWNERs pushes the button :-)

[lucacavallaro]

I propose to change the ring from adopt to trial

When Gherkin will be used outside idpay we can move it to adopt

[iwoak]

@lucacavallaro I was thinking the same thing but then I made this query https://github.com/search?q=org%3Apagopa+language%3AGherkin&type=code
pagoPA, idpay, interop, pn :O

@GiovanniMancini @pasqualespica @infantesimone does you confirm? are you using with satisfaction Gherkin?

[lucacavallaro]

@iwoak ok, do you filtered out the contributions made by consultants? they often bring into our stack their technologies, but then we do not adopt them

[iwoak]

@lucacavallaro nope, but I asked to the internal member of those products whether it was our conscious choice.

@ruggerocastagnola I noticed that you and your team used it, feedback?

[ZorbaDimatteo]

joining the discussion: in pn we use gherkin (proposed by consultant but adopted by team) because it's easier for our QA team to write and discuss test cases with developers, but also to analyze the results of e2e automatic tests more easily

[gunzip]

@ZorbaDimatteo may you share a link to PN repo(s) pointing to tests?

[ZorbaDimatteo]

@gunzip sure!
here they are
https://github.com/pagopa/pn-b2b-client
https://github.com/pagopa/pn-frontend-e2e

[balanza]

I like the entry, thanks @TommasoLencioni

I propose just a couple of possible, optional refinements, if you find them useful:

1. review the list of repositories that use gherkin
2. differentiate "use cases" (a list of scenario in which we suggest Gherkin to be an proper solution) from "actual usage" (the list of using repos); this should help readers fit Gherkin in their solutions

[gunzip]

I've added the link provided by @iwoak that lists all repos that use Gherkin.

I'd vote to merge this one as is, then refine the entry according to:

differentiate "use cases" (a list of scenario in which we suggest Gherkin to be an proper solution) from "actual usage" (the list of using repos); this should help readers fit Gherkin in their solutions