Oleg Pidsadnyi

After reading the ember-data source I see this can be done by wrapping the response in an object with the key with the same name as the name of the...

After I wrapped them - they are recognized well. But indeed, it would prefer to specify the type separately like according to the doc: `store.pushPayload("order", data)` If you read the...

Another thing is.. If I'll post something which is not exactly my model to create my model it would be nice to get it's primary key. When I do pushPayload...

@youtux I'm not sure about this mapping of the text files to py files. When we started on pytest-bdd that was what made it different from the others. Especially when...

@uriyyo the entry point to pytest tests is test_X.py files. What's wrong with that. You can place a function there like scenarios that would explode to the test items. The...

@uriyyo pytest-bdd is pytest in the first place. There's no goal to compete with behave at all

@uriyyo On the other hand if .feature files are underneath the tests dir we could build a support to collect them as the doc suggesting https://docs.pytest.org/en/latest/example/nonpython.html I don't like modality...

I don't mind if we are making a breaking change. But of course then we need to rewrite the doc a bit.

@elchupanebrej have a look. I started sketching out some preparations for the multiple scenario examples

Scenarios is just a shortcut to collect all the scenarios from feature file (s) and turn them into the test items. So you can include them in your test_*.py files...