Hi Ronny, About reusable test suites, what I have done is to put the required tests/checks into fixtures or even classes which are importable across projects and reused there. Could you provide a more specific example of the problem you see?
About the collection roots, I also didn't quite get what you mean... I think some examples would also be helpful. :) Cheers, Bruno. On Sun, Jan 24, 2016 at 9:47 PM Ronny Pfannschmidt < [email protected]> wrote: > Hi everyone, > > a topic thats gripping since quite a while, is wanting to have reusable > testsuites, > so plugins/extensions that implement a behaviout, > can import and use integration tests from a installed package, > and use them in a different configuration > > another detail that plays into that is certain plugins needing different > collections as well > an example is the doctest-module, which should scan for doctests in the > installed modules > that where imported, and not the ones in the working directory. > > unfortunately its hard to find a good way to express those configured > roots for collection, > since the ini format on its own is rather limited, and i would like to > avoid introducing sub-languagess > > -- Ronny > _______________________________________________ > pytest-dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/pytest-dev >
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
