You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Install the required libraries: pip install "pytest==8.3.5" "pytest-asyncio==0.26.0" "pytest-playwright==0.7.0" "playwright==1.51.0"
Run playwright install.
Save the minimal Python code above as tests/test_minimal_playwright_route.py.
Save the pytest.ini content in the project root.
Run the test from the project root using the command: pytest -v -s tests/test_minimal_playwright_route.py
Expected behavior
Expected Result:
The test execution should print the following logs (or similar) and eventually complete or fail during navigation/timeout:
LOG: Minimal Test (pytest-playwright) - START
LOG: Minimal Test (pytest-playwright) - Setting up route interception...
LOG: Minimal Test (pytest-playwright) - Route interception setup COMPLETE.
LOG: Minimal Test (pytest-playwright) - Navigating to example.com...
Actual behavior
Actual Result:
The test execution prints the following and then hangs indefinitely. It never proceeds past the await page.route(...) call and must be manually interrupted (Ctrl+C).
LOG: Minimal Test (pytest-playwright) - START
LOG: Minimal Test (pytest-playwright) - Setting up route interception...
I was not able to reproduce that it hangs indefinitely. For me it was throwing after 10s. Are you intentionally not calling continue/fulfill etc. in the route handler?
Version
1.51.0
Steps to reproduce
Code Snippet
Libraries Used:
Steps to Reproduce:
pip install "pytest==8.3.5" "pytest-asyncio==0.26.0" "pytest-playwright==0.7.0" "playwright==1.51.0"
playwright install
.tests/test_minimal_playwright_route.py
.pytest.ini
content in the project root.pytest -v -s tests/test_minimal_playwright_route.py
Expected behavior
Expected Result:
The test execution should print the following logs (or similar) and eventually complete or fail during navigation/timeout:
Actual behavior
Actual Result:
The test execution prints the following and then hangs indefinitely. It never proceeds past the
await page.route(...)
call and must be manually interrupted (Ctrl+C).Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: