On Mon, 1 Jul 2019, Bruno Oliveira wrote:
Hmmm strange, because for "pytest.config" to be available, it means the
user is running the "pytest" command.
Yes, they are, but in the package within which the tests are created
and loaded, pytest_configure is not called because it is not a test
nor p
On Mon, Jul 1, 2019 at 9:21 AM Chris Dent wrote:
> On Mon, 1 Jul 2019, Bruno Oliveira wrote:
> > On Mon, Jul 1, 2019 at 8:17 AM Chris Dent wrote:
> > Is Gabbi + pytest a plugin? If so, you could store the config object
> during
> > pytest_configure to reuse later:
>
> Thanks for the quick respon
On Mon, 1 Jul 2019, Bruno Oliveira wrote:
On Mon, Jul 1, 2019 at 8:17 AM Chris Dent wrote:
Is Gabbi + pytest a plugin? If so, you could store the config object during
pytest_configure to reuse later:
Thanks for the quick response.
It's sort of a plugin. It uses plugin mechanisms to manage the
Hi Chris,
On Mon, Jul 1, 2019 at 8:17 AM Chris Dent wrote:
>
> That uses the now deprecated `pytest.config` global and I'm
> struggling to determine how best to replace it without having to
> make changes to the calling patterns that would break compatibility
> with existing test installations.
I maintain gabbi [1], a YAML driven HTTP API tester that dynamically
creates test cases in ordered suites. It was originally created to
work in a unittest/testtools/testrepository environment and then had
pytest support hacked in later. It does some shall we say unorthodox
things to work in both
