No Scenario Outline about pytest-bdd HOT 10 CLOSED

yes, it's possible in pytest-bdd via parametrization:
https://github.com/olegpidsadnyi/pytest-bdd#step-parameters

On 27 September 2013 09:47, apoh [email protected] wrote:

Currently it's only possible to add parameter for a step or scenario via
the testcode. Gherkin support the feature of "Scenario Outline"
http://docs.behat.org/guides/1.gherkin.html#scenario-outlines add
different datasets to the feature-file. Is there a way to implement this?

P.S.: If you need support I can help you.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23
.

Anatoly Bubenkov

from pytest-bdd.

ah, sorry you meant to have dataset in the scenario file directly...
well, it will need the casting from strings to some python types in
general...
do you see the real value in this?
can you describe the use-case?
eg why having parameter values in python is worse than having dataset in
scenario file?

On 27 September 2013 10:02, Anatoly Bubenkov [email protected] wrote:

yes, it's possible in pytest-bdd via parametrization:
https://github.com/olegpidsadnyi/pytest-bdd#step-parameters

On 27 September 2013 09:47, apoh [email protected] wrote:

Currently it's only possible to add parameter for a step or scenario via
the testcode. Gherkin support the feature of "Scenario Outline"
http://docs.behat.org/guides/1.gherkin.html#scenario-outlines add
different datasets to the feature-file. Is there a way to implement this?

P.S.: If you need support I can help you.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23
.

Anatoly Bubenkov

Anatoly Bubenkov

from pytest-bdd.

We advocate the standard pytest parametrization (pytest.mark.parametrize) where you can use complex Python types. For example if you operate some Point(x, y) type configuring them in the txt would be not easy.

If you have strong reasons to define the Example section in the .feature file please share.

from pytest-bdd.

Yes I think there's a real value. In example when a ProducOwner who only is able to write Gherkin-Feature files, like to test different datasets.

Okay so I will open a fork and send u a pull-request when I'm done.

from pytest-bdd.

It will be problematic as we only parse files on runtime, not importtime
and we rely on pytest parametrization
so to continue to rely on pytest parametrization you will need to parse files on import time, which i have to say is not good approach

from pytest-bdd.

So you'r parsing Step by Step!? Maybee there is a way to look for the
Examples-Section when a Scenario is starting.

Am 27.09.2013 10:33, schrieb Anatoly Bubenkov:

It will be problematic as we only parse files on runtime, not importtime
and we rely on pytest parametrization
so to continue to rely on pytest parametrization you will need to parse
files on import time, which i have to say is not good approach

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

Andreas Pohle

Mail: [email protected]
Skype: andreas_po
Mobile: 0163/1769321
Phone: 030/69200891

from pytest-bdd.

not step by step but first touch of the file happens too late for the
parametrization

On 27 September 2013 10:39, apoh [email protected] wrote:

So you'r parsing Step by Step!? Maybee there is a way to look for the
Examples-Section when a Scenario is starting.

Am 27.09.2013 10:33, schrieb Anatoly Bubenkov:

It will be problematic as we only parse files on runtime, not importtime
and we rely on pytest parametrization
so to continue to rely on pytest parametrization you will need to parse
files on import time, which i have to say is not good approach

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

Andreas Pohle

Mail: [email protected]
Skype: andreas_po
Mobile: 0163/1769321
Phone: 030/69200891

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23#issuecomment-25230653
.

Anatoly Bubenkov

from pytest-bdd.

pytest parametrization works the way it generates code, basically
Well, im sure it's possible (to add what you want), just not as easy as you
might think

On 27 September 2013 10:39, apoh [email protected] wrote:

So you'r parsing Step by Step!? Maybee there is a way to look for the
Examples-Section when a Scenario is starting.

Am 27.09.2013 10:33, schrieb Anatoly Bubenkov:

It will be problematic as we only parse files on runtime, not importtime
and we rely on pytest parametrization
so to continue to rely on pytest parametrization you will need to parse
files on import time, which i have to say is not good approach

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

Andreas Pohle

Mail: [email protected]
Skype: andreas_po
Mobile: 0163/1769321
Phone: 030/69200891

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/23#issuecomment-25230653
.

Anatoly Bubenkov

from pytest-bdd.

Ok, I will see what i can do

Am 27.09.2013 10:41, schrieb Anatoly Bubenkov:

pytest parametrization works the way it generates code, basically
Well, im sure it's possible (to add what you want), just not as easy as you
might think

On 27 September 2013 10:39, apoh [email protected] wrote:

So you'r parsing Step by Step!? Maybee there is a way to look for the
Examples-Section when a Scenario is starting.

Am 27.09.2013 10:33, schrieb Anatoly Bubenkov:

It will be problematic as we only parse files on runtime, not
importtime
and we rely on pytest parametrization
so to continue to rely on pytest parametrization you will need to parse
files on import time, which i have to say is not good approach

—
Reply to this email directly or view it on GitHub
<

#23 (comment)

.

Andreas Pohle

Mail: [email protected]
Skype: andreas_po
Mobile: 0163/1769321
Phone: 030/69200891

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/23#issuecomment-25230653

.

Anatoly Bubenkov

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

Andreas Pohle

Mail: [email protected]
Skype: andreas_po
Mobile: 0163/1769321
Phone: 030/69200891

from pytest-bdd.

starting on this issue
stay tuned :)

from pytest-bdd.