pathsin the behave configuration, but this is mainly because we have BDD tests in two different places.
PYTHONPATH=$PYTHONPATH:$(pwd)/features/steps behavebut that seems strange, and (perhaps unrelatedly) that failed when I tried it on Travis, saying it couldn't find the module.
behave.ini, and have an
tests, behave would load features from
tests/stuff.pywould be importable as
tests.stuff, or perhaps
stuff? I see
from test_app.models import BehaveTestModel, and
tests/test_appis named in
tox.iniof the project.
Formatter must be importable from python search path.. Is that the general python search path, or the python search path with the paths from
def before_scenario(context, scenario): """ Hanlder before the test scenario is run """ logging.info("Starting Scenario: %s", scenario.name) if scenario.name == 'Test PGaaS Product': use_fixture(provision_product, context) @capture def before_step(context, step): """ Handler before the test step is run """ logging.info("Starting Step: %s", step.name) if step.name == 'Create a clone of the cluster': use_fixture(provision_clone, context)
for row in context.example: print(row)
behave @listfile.txtwhich reads the list of feature files of FileLocations from the textual file „listfile.txt“. But if you want to run all examples of a ScenarioOutline or the complete ScenarioOutline, why do you not use tags ? Your initial question was that you want to run one Example row in a ScenarioOutline.
behavefor system tests or integration tests (not for ATDD or BDD) ?!?
I'm think about extentions. Like pytest has with
pluggy. Many projects has insane envrionment files.
@jenisys, what we think about implement a plugin manager for hooks?
I try explain my idea on this project https://github.com/dunossauro/hook_plug.
Something like install plugins in hooks and inside de plugins you can implamente modules and then put context variables and execute routines in hooks