I often get requests from developers and others to test some scenarios to check if a web app functions correctly. Generally, these scenarios don't have enough details and I have to waste a lot of time in getting information that should have already been given to me. So, I was thinking of forcing the entire organization to communicate such scenarios in Gherkin format, as shown below.
GIVEN the conditions condition-1, condition-2, condition-3 etc., WHEN these actions action-1, action-2, action-3 etc. are performed, THEN these events occur event-1, event-2, event-3 etc.
This format seems very helpful in that it will make scenarios clear and reduce the need for unnecessary communication to find out the GIVEN, WHENS and THENS that one needs to know before they test something.
But, since I have limited experience in using Gherkin, I am not sure if Gherkin is the best way to communicate scenarios in all kinds of situations. I don't know if there are any better methods out there. So, what is the best way to write testing scenarios ?