My colleague and I are having a debate about when its appropriate to use the 'background' keyword.
the test scenario is to confirm that the correct country codes appear when you enter a telephone number.
Now the way the test script was written in a way that was so vague it wasn't immediately apparent what it was supposed to do. I spoke to the author of the test and got more clarification.
As our product is so large (100 + countries). I managed to reduct it down to 10 countries. This will require me to create 10 accounts and ensure they are verified.
My question is this. As the this test is so initially super vague it would make sense to create a 'background gherkin' step that will clarify that it will only be for 10 regions and to list those regions so that anyone else who picks up the test will know exactly what this test is supposed to do. I admit that it's one scenario but it is a critical scenario so it's essential that stake holders know what we are trying to achieve and what countries were chosen.
On the other hand, my colleague believe that a background step is needed when multiple scenarios in the feature file has same GIVEN clause and we can move such a STEP to single BACKGROUND clause in the beginning of the feature file.
In this instance, what do you advise? Given the critical nature of the scenario, the vagueness of the way the test is written.