-
Notifications
You must be signed in to change notification settings - Fork 64
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Expose output_dir as a fixture #227
Comments
which trace.json file do you want to add? The code is currently not exposed, but we could maybe expose it, so its something like we do upstream in Node.js - like playwright-pytest/pytest_playwright/pytest_playwright.py Lines 183 to 191 in 6d624fc
You could probably import the function from your test as a workaround for now. |
@mxschmitt I just want to add my browser traces I enable with cdp. It would be great to make full trace output folder path an attribute of the context object. Can I assume that
|
Its more public by accident. If we were to expose output_dir, then as a fixture. I'd recommend to import |
馃殌 Feature Request
I could not find how to get a handle to the names playwright generates for its output folders under "test-results". I would think the browser context or something would have a property I could access to get the dynamically generated
test-results/<TEST_NAME_SANITIZED>/trace.zip
I want to colocate browser trace json files in the same folder with the playwright trace files. The problem is I can't find docs on how playwright sanitizes and generates the test specific folders- I also don't want to have to duplicate that code myself just so I can do this:
I don't want to try to generate
<Path under test-results where the trace.zip will be located>
myself.How do I control the naming of these folders OR get a handle to their paths from playwright? Seems like this feature does not exist right?
Example
No response
Motivation
I want to colocate browser trace json files in the same folder with the playwright trace files so my test results aren't scattered around everywhere.
The text was updated successfully, but these errors were encountered: