Auto-create scenario test functions

[santagada]

pytest-bdd would be much more awesome if it would auto create scenario functions, so you wouldn't have to define empty functions just to make the test go. I think this either could be implemented as a test collector (also would make the test reporter more user friendly as it would show the feature file as the source of tests) or it could be just a invocation form of scenario function like:

scenario('feature/something.feature', auto=True)

[bubenkoff]

But there's auto generation for that
Did you try it?
On Mar 16, 2015 7:12 PM, "Leonardo Santagada" notifications@github.com
wrote:

pytest-bdd would be much more awesome if it would auto create scenario
functions, so you wouldn't have to define empty functions just to make the
test go. I think this either could be implemented as a test collector (also
would make the test reporter more user friendly as it would show the
feature file as the source of tests) or it could be just a invocation form
of scenario function like:

scenario('feature/something.feature', auto=True)

—
Reply to this email directly or view it on GitHub
#103.

[blueyed]

@bubenkoff
Are you referring to https://github.com/pytest-dev/pytest-bdd/blob/master/README.rst#test-code-generation-helpers?

I think what @santagada is a bit more involved (if I understand it correctly): the advanced code generator would say "Scenario is not bound to any test":

Please place the code above to the test file(s):

@scenario('tests/generation.feature', 'Code is generated for scenarios which are not bound to any tests')
def test_Code_is_generated_for_scenarios_which_are_not_bound_to_any_tests():
    """Code is generated for scenarios which are not bound to any tests."""

But this seems to be redundant. It would be nice if the scenario files could
be considered to be (pytest) tests automatically.

[bubenkoff]

Yes I'm about that
I wanted all of interested people to play with existing possibilities first.
I'm more than open for the change, just it should really improve things.
On Mar 16, 2015 10:46 PM, "Daniel Hahler" notifications@github.com wrote:

@bubenkoff https://github.com/bubenkoff
Are you referring to
https://github.com/pytest-dev/pytest-bdd/blob/master/README.rst#test-code-generation-helpers
?

I think what @santagada https://github.com/santagada is a bit more
involved (if I understand it correctly): the advanced code generator would
say "Scenario is not bound to any test":

Please place the code above to the test file(s):

@Scenario('tests/generation.feature', 'Code is generated for scenarios which are not bound to any tests')
def test_Code_is_generated_for_scenarios_which_are_not_bound_to_any_tests():
"""Code is generated for scenarios which are not bound to any tests."""

But this seems to be redundant. It would be nice if the scenario files
could
be considered to be (pytest) tests automatically.

—
Reply to this email directly or view it on GitHub
#103 (comment)
.

[blueyed]

Cool.

What are your current thoughts on providing this?
I see that behave does this automatically.

I've thought that maybe pytest would require the test functions to collect any tests, but that can be certainly hooked into / provided in a different way.

[bubenkoff]

there are discussions in #89 and #92

[blueyed]

I like the idea from #90 (comment), where you would import / create tests for a set of scenarios:

scenarios('my.feature')

This could then also support using directories (with or without recursion), which would allow to set up all features like:

scenarios()

And for directories:

scenarios('frontend', recurse=True)  # recurse=True could be the default

It's probably useful to also accept an iterable here, allowing to fine tune it using some generators etc.

(please keep in mind that I am new to pytest-bdd, so am lacking any experience in this regard)

[bubenkoff]

this will only work for simple cases, but if you'll need to parametrize certain test directly on the function level, then you'll need a way to exclude certain test from that automatic 'suite'

[santagada]

The problem with the generator is that it is too manual. There should be some way to auto collect tests, just like py.test does for functions and all.

[bubenkoff]

I'll try to experiment with this (again)

[santagada]

It is starting to look good 👍