-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Environment not filled in on tests #334
Comments
Has it ever worked? |
I don't have the ability to dive in deeper. |
I will look into this, have a personal need for it. I would imagine there is NOTHING stopping you from creating your own environment.xml at runtime and dropping it into the allure results folder, as the command line generator should not care, its language agnostic (IIRC tho its been a while). |
def _set_allure_environment(self) -> SomeObject:
if 'allure-dir' in os.environ:
with open(os.path.join(os.environ['allure-dir'], self._ENVIRONMENT_FILE), 'w+') as stream:
stream.write('processes: {}\n'.format(os.getenv('processes')))
else:
log.info("No --allure-dir was specified so we are skipping the reporting properties")
return self here is a small snippet that makes it possible, as specified just drop the properties file into the allure-dir |
Duplicate of #96 |
In my test, I put:
import pytest
import allure
def pytest_configure(config):
allure.environment(url='site.com', browser=u'Google Chrome')
I ran the test, and environment was not filled in.
http://imgur.com/a/licky
The text was updated successfully, but these errors were encountered: