Unable to start the tests with allure-pytest 2.0 from command line through python about allure-python

[sseliverstov]

Try this, please

pytest ./tests/e2e --alluredir=./report --allure-features=Setup

[OlegKuzovkov]

I have some strange internal import problems with command above.

[sseliverstov]

maybe check installation

MacBook-Pro-Stas:allure2 stasseliverstov$ python
Python 2.7.13 (default, Feb 20 2017, 21:56:15)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from allure_pytest import listener
>>> dir(listener)
['AllureListener', 'AllureLogger', 'FinalizerSpy', 'ItemCache', 'Label', 'Link', 'Parameter', 'Status', 'StatusDetails', 'TestAfterResult', 'TestBeforeResult', 'TestResult', 'TestResultContainer', 'TestStepResult', '__builtins__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '_test_fixtures', 'allure_full_name', 'allure_labels', 'allure_links', 'allure_package', 'allure_parameters', 'md5', 'now', 'pytest', 'uuid4']
>>>

[OlegKuzovkov]

Spares-MacBook-Pro:thirdshelf-qa-framework olehkuzovkov$ python3
Python 3.5.1 (v3.5.1:37a07cee5969, Dec  5 2015, 21:12:44) 
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from allure_pytest import listener
>>> dir(listener)
['AllureListener', 'AllureLogger', 'FinalizerSpy', 'ItemCache', 'Label', 'Link', 'Parameter', 'Status', 'StatusDetails', 'TestAfterResult', 'TestBeforeResult', 'TestResult', 'TestResultContainer', 'TestStepResult', '__builtins__', '__cached__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__spec__', '_test_fixtures', 'allure_full_name', 'allure_labels', 'allure_links', 'allure_package', 'allure_parameters', 'md5', 'now', 'pytest', 'uuid4']
>>> 

[sseliverstov]

Where its fails? Hooks? Fixtures? Steps?

[sseliverstov]

ping =)

[OlegKuzovkov]

Before running test using pytest command, we need to add project root to the PYTHONPATH. IDEA does this automatically for you, but when you start your tests from cmd - you have to take care about this by yourself. I'm trying to find a way how to do this right now. Will get back you once I found a workaround.

[sseliverstov]

Possibly fixed in 2.1.0.b1. Reopen please if still reproduced