Hello All, Is it a good practice to create Scenario per Feature file?

8 views
Skip to first unread message

sundresh

unread,
Mar 4, 2020, 4:55:46 PM3/4/20
to spe...@googlegroups.com
I am in the midst of automation about 500 test cases and am putting all Scenarios (test case) in the same .Feature file.

Although am getting pushed towards using One Feature file per Scenario which I am not very happy with. What is the right approach here? 

Lohit Anand

unread,
Mar 4, 2020, 5:10:54 PM3/4/20
to spe...@googlegroups.com
I did it based on epic 

On Thu, 5 Mar 2020 at 8:55 am, sundresh <msun...@gmail.com> wrote:
I am in the midst of automation about 500 test cases and am puttng all Scenarios (test case) in the same .Feature file.

Although am getting pushed towards using one Feature file per Scenario. What is the right approach here? 

--
You received this message because you are subscribed to the Google Groups "SpecRun" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specrun+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/specrun/51d85833-4d37-4bcd-a832-2ae0b263e620%40googlegroups.com.

David Khokhar

unread,
Mar 4, 2020, 5:28:16 PM3/4/20
to spe...@googlegroups.com
I tend to agree with Lohit although I let the story cards drive my decision. Typically high level functional requirements are defined at the Epic level if multiple streams of work effort is required. I create end to end tests at the bdd feature level but if there are smaller story components which require say lower level technology testing. Then I create a seperate feature for that because in many cases those feature files are reusable so it just makes it a little easier to cherry pick for later projects. But ultimately I think the breakdown should simply reflect how your company is breaking down the testing

Sent from my iPhone

On 5 Mar 2020, at 8:10 am, Lohit Anand <lohit.a...@gmail.com> wrote:



Eliezer Cazares

unread,
Mar 4, 2020, 6:11:01 PM3/4/20
to spe...@googlegroups.com
There's a reason we test features. 
Agile is based on small increments.
With specflow, you typically should write your Feature files before development works on the code for the given Feature.

If you are doing regression backlog as a new hire, try and acommodate per feature if possible.

Reply all
Reply to author
Forward
0 new messages