local-it/kolli-config
local-it/kolli-config
1
0
Fork 0
Code Issues 1 Pull requests 2 Projects Releases Packages Wiki Activity

chore(deps): update dependency pytest-playwright to v0.10.0 #115

Open
renovate wants to merge 1 commit from renovate/pytest-playwright-0.x into main
pull from: renovate/pytest-playwright-0.x
merge into: local-it:main
Conversation 0 Commits 1 Files changed 1 +1 -1
renovate commented 2026-10-09 01:01:11 +02:00
Collaborator
Copy link

This PR contains the following updates:

Package Change Age Confidence
pytest-playwright ==0.9.0 → ==0.10.0 age confidence

Release Notes

microsoft/playwright-pytest (pytest-playwright)

v0.10.0

Compare Source

Highlights

Traces for playwright.request API contexts (#​333). --tracing now also records contexts created with playwright.request.new_context(), one chunk per test, so a session-scoped API context yields a trace per test. The traces follow the same retain-on-failure handling, trace-N.zip naming and report attachments as browser traces. Requires Playwright 1.60 or newer.

Artifacts in test reports (#​332). Kept screenshots, videos and traces are added to the teardown report as playwright_screenshot, playwright_video and playwright_trace user properties, so --junitxml writes them as <property> elements and pytest_runtest_logreport hooks and reporters can pick them up. With pytest-html >= 4 they are linked from the report, and embedded with --self-contained-html.

Reruns keep their own artifacts (#​331). With pytest-rerunfailures, every attempt now writes to its own folder, test-results/<test>-retry1/ and so on, like Playwright Test. Attempts no longer overwrite each other.

Artifacts survive fixture failures in teardown (#​330). --tracing retain-on-failure, --video retain-on-failure and --screenshot only-on-failure now keep artifacts when a fixture fails during teardown. A test skipped from a fixture no longer counts as failed.

Per-test browser launch options (#​329):

@&#8203;pytest.mark.parametrize(
    "browser_type_launch_args",
    [{"args": ["--lang=de-DE"]}],
    indirect=True,
)
def test_german(page):
    ...

Each distinct value launches its own browser; command line options such as --headed and --slowmo still apply.

Multi-browser parametrization fixes. Overriding the page fixture no longer drops --browser parametrization on older pytest versions (#​314). browser_name is now parametrized indirectly, so tests keep their original order within a browser (#​284).

VS Code debugger (#​328). The browser is launched headed under the debugger only when a display is available. On Linux without DISPLAY or WAYLAND_DISPLAY set, it stays headless unless --headed is passed.

Breaking changes

  • pytest-base-url is now an optional dependency (#​334). The plugin provides --base-url, the base_url ini option, the PYTEST_BASE_URL environment variable and the base_url fixture on its own. --verify-base-url needs the extra:

    pip install pytest-playwright[base-url]

  • Minimum pytest version is 7.0 for pytest-playwright and 8.2 for pytest-playwright-asyncio (#​333).

  • python-slugify 9.x is now supported (#​324).

Full Changelog: https://github.com/microsoft/playwright-pytest/compare/v0.9.0...v0.10.0

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest-playwright](https://github.com/microsoft/playwright-pytest) | `==0.9.0` → `==0.10.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest-playwright/0.10.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest-playwright/0.9.0/0.10.0?slim=true) | --- ### Release Notes <details> <summary>microsoft/playwright-pytest (pytest-playwright)</summary> ### [`v0.10.0`](https://github.com/microsoft/playwright-pytest/releases/tag/v0.10.0) [Compare Source](https://github.com/microsoft/playwright-pytest/compare/v0.9.0...v0.10.0) #### Highlights **Traces for `playwright.request` API contexts** ([#&#8203;333](https://github.com/microsoft/playwright-pytest/issues/333)). `--tracing` now also records contexts created with `playwright.request.new_context()`, one chunk per test, so a session-scoped API context yields a trace per test. The traces follow the same `retain-on-failure` handling, `trace-N.zip` naming and report attachments as browser traces. Requires Playwright 1.60 or newer. **Artifacts in test reports** ([#&#8203;332](https://github.com/microsoft/playwright-pytest/issues/332)). Kept screenshots, videos and traces are added to the teardown report as `playwright_screenshot`, `playwright_video` and `playwright_trace` user properties, so `--junitxml` writes them as `<property>` elements and `pytest_runtest_logreport` hooks and reporters can pick them up. With pytest-html >= 4 they are linked from the report, and embedded with `--self-contained-html`. **Reruns keep their own artifacts** ([#&#8203;331](https://github.com/microsoft/playwright-pytest/issues/331)). With pytest-rerunfailures, every attempt now writes to its own folder, `test-results/<test>-retry1/` and so on, like Playwright Test. Attempts no longer overwrite each other. **Artifacts survive fixture failures in teardown** ([#&#8203;330](https://github.com/microsoft/playwright-pytest/issues/330)). `--tracing retain-on-failure`, `--video retain-on-failure` and `--screenshot only-on-failure` now keep artifacts when a fixture fails during teardown. A test skipped from a fixture no longer counts as failed. **Per-test browser launch options** ([#&#8203;329](https://github.com/microsoft/playwright-pytest/issues/329)): ```python @&#8203;pytest.mark.parametrize( "browser_type_launch_args", [{"args": ["--lang=de-DE"]}], indirect=True, ) def test_german(page): ... ``` Each distinct value launches its own browser; command line options such as `--headed` and `--slowmo` still apply. **Multi-browser parametrization fixes.** Overriding the `page` fixture no longer drops `--browser` parametrization on older pytest versions ([#&#8203;314](https://github.com/microsoft/playwright-pytest/issues/314)). `browser_name` is now parametrized indirectly, so tests keep their original order within a browser ([#&#8203;284](https://github.com/microsoft/playwright-pytest/issues/284)). **VS Code debugger** ([#&#8203;328](https://github.com/microsoft/playwright-pytest/issues/328)). The browser is launched headed under the debugger only when a display is available. On Linux without `DISPLAY` or `WAYLAND_DISPLAY` set, it stays headless unless `--headed` is passed. #### Breaking changes - **`pytest-base-url` is now an optional dependency** ([#&#8203;334](https://github.com/microsoft/playwright-pytest/issues/334)). The plugin provides `--base-url`, the `base_url` ini option, the `PYTEST_BASE_URL` environment variable and the `base_url` fixture on its own. `--verify-base-url` needs the extra: ```sh pip install pytest-playwright[base-url] ``` - **Minimum pytest version** is 7.0 for pytest-playwright and 8.2 for pytest-playwright-asyncio ([#&#8203;333](https://github.com/microsoft/playwright-pytest/issues/333)). - `python-slugify` 9.x is now supported ([#&#8203;324](https://github.com/microsoft/playwright-pytest/issues/324)). **Full Changelog**: <https://github.com/microsoft/playwright-pytest/compare/v0.9.0...v0.10.0> </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNDguMyIsInVwZGF0ZWRJblZlciI6IjQzLjE2NS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWF0ZWQiLCJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZSJdfQ==-->
chore(deps): update dependency pytest-playwright to v0.10.0
Some checks failed
continuous-integration/drone/pr Build is failing
Details
df266a2fa0
renovate scheduled this pull request to auto merge when all checks succeed 2026-10-09 01:01:11 +02:00
Some checks failed
continuous-integration/drone/pr Build is failing
Required
Details
Some required checks were not successful.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/pytest-playwright-0.x:renovate/pytest-playwright-0.x
git switch renovate/pytest-playwright-0.x
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
local-it/kolli-config!115
No description provided.