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.

Sign up for GitHub

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

Jump to bottom

Allow custom (re)initialization for Allure lifecycle #497

Open

delatrie opened this issue May 8, 2024 · 0 comments

Labels

task:new feature theme:core

Contributor

delatrie commented May 8, 2024

Context

Currently, AllureLifecycle is initialized once per process. The static singleton is then used until the process ends.

The following scenarios are not supported due to such limitations:

Provide a user-defined initialization to specify the following at runtime:
- a configuration, including the results directory (although, a workaround exists).
- a writer (e.g., a message-based writer instead of the file system one).
Executing separate test framework runs in-process (see discussion 2536):
- There is no way to reconfigure the lifecycle once it's created.
- There is no way to isolate lifecycles for separate parallel in-process runs.

delatrie added theme:core task:new feature labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment