Repository navigation
[BUG] Tracing does not work with playwright.request.newcontext() #137
Description
Context:
I am using playwright to test REST API endpoints.
I do not see trace.zip after I run pytest --tracing=on.
Code Snippet
Simple test script
import os
from typing import Generator
import pytest
from playwright.sync_api import Playwright, APIRequestContext
@pytest.fixture(scope="session")
def api_request_context(
playwright: Playwright,
) -> Generator[APIRequestContext, None, None]:
request_context = playwright.request.new_context(
base_url="https://api.publicapis.org",
ignore_https_errors=True
)
yield request_context
request_context.dispose()
def test_should_create_bug_report(api_request_context: APIRequestContext) -> None:
response = api_request_context.get("/entries")
assert response.okDescribe the bug
pytest --tracing=on test_mytest.py does not produce trace.zip
Activity
QuLogic commentedon Nov 4, 2022
AFAICT, it also doesn't work with
Browser.new_context(e.g., using thebrowserfixture to create a context with a different scale factorbrowser.new_context(device_scale_factor=2)); not sure if that ends up using the sameAPIRequestContextin the end.Edit: Ah, maybe what I'm seeing is #99.
guandalf commentedon Feb 20, 2024
And this is particularly problematic as the only way to test chrome extensions is by creating a new context as per https://playwright.dev/python/docs/chrome-extensions
Please help :)
guandalf commentedon Feb 20, 2024
In fact I just reimplemented my fixture copying it from
playwright-pytest/pytest_playwright/pytest_playwright.py
Line 232 in fb2e7c7
ltsuda commentedon Oct 9, 2024
I've found the same issue, if this is not by design.
It appears that we should use fixture
new_context, so tracing/videos/screenshots are taken automatically if enabled butnew_contextis afunctionfixture and notsession.#232
#216
shisrafilov commentedon Oct 24, 2024
The issue is still there
feat: record traces of playwright.request API contexts
feat: record traces of playwright.request API contexts (#333)