The tests fail for now, but not entirely.
Volunteers wanted for alpha-testing on real suites.

This is it -- now all tests are run locally (wtih no xdist) and with xdist 's -n 1 -- and that means that all the features work totally same with xdist!

@FuriousDuck @mavlyutov @hmax @alvassin @bayandin @dimonb please take a look and try this one branch with your test-suite -- real-data-base feedback would be priceless.

What is more important -- so far code is a little bit screwed up in regards to previously-used architecture -- the Common module is not that used, some hacking is done in the pytest plugin, etc, etc.
Any architectural advice would be greatly appreciated.

Volunteers wanted for alpha-testing on real suites.

mine projects build okay with xdist enabled, their allure reports look okay too.
thanks for the long-awaited feature!

Okay, so the important part is about the internal workings of the implementation.
How shall we rule the fate of allure.common.AllureImpl? The data flow it was designed for is no longer the case in the py.test plugin -- should we keep that "basic" implementation for the sake of, say, allure-nose support? Or should it be re-imagined to actually mean something (be it of less sense than now)?