Skip to content

Conversation

@thomhurst
Copy link
Owner

This PR contains the following updates:

Package Type Update Change
Microsoft.Playwright nuget minor 1.56.0 -> 1.57.0

Release Notes

microsoft/playwright-dotnet (Microsoft.Playwright)

v1.57.0

Chrome for Testing

Starting with this release, Playwright switches from Chromium, to using Chrome for Testing builds. Both headed and headless browsers are subject to this. Your tests should still be passing after upgrading to Playwright 1.57.

We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.

new and old logo

If you still see an unexpected behaviour change, please file an issue.

On Arm64 Linux, Playwright continues to use Chromium.

Breaking Change

After 3 years of being deprecated, we removed Page.Accessibility from our API. Please use other libraries such as Axe if you need to test page accessibility. See our Node.js guide for integration with Axe.

New APIs

Browser Versions

  • Chromium 143.0.7499.4
  • Mozilla Firefox 144.0.2
  • WebKit 26.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.

@thomhurst thomhurst added dependencies Pull requests that update a dependency file MINOR renovate-bot labels Dec 4, 2025
Copilot AI review requested due to automatic review settings December 4, 2025 21:38
@thomhurst thomhurst added dependencies Pull requests that update a dependency file renovate-bot MINOR labels Dec 4, 2025
@thomhurst thomhurst enabled auto-merge (squash) December 4, 2025 21:38
@claude
Copy link
Contributor

claude bot commented Dec 4, 2025

Claude finished @thomhurst's task —— View job


Reviewing Playwright Dependency Update

I'll review this Microsoft.Playwright dependency update from v1.56.0 to v1.57.0 and check for potential impacts on the codebase.

Todo List:

  • Read the changed file (Directory.Packages.props)
  • Search for any usage of the deprecated Page.Accessibility API
  • Review Playwright-related code in the project
  • Check for potential breaking changes impact
  • Provide comprehensive review feedback

Review Feedback

Code Quality & Best Practices

  • Clean Dependency Update: The change is minimal and isolated to the version number in Directory.Packages.props:38
  • Centralized Package Management: Using centralized package management is a good practice for maintaining consistent versions across the solution
  • Automated Updates: Using Renovate bot for dependency updates is excellent for keeping dependencies current

Breaking Changes Assessment

  • ✅ No Impact: The major breaking change in v1.57.0 is the removal of Page.Accessibility API after 3 years of deprecation
  • ✅ Clean Codebase: I searched the entire codebase and found no usage of the deprecated Page.Accessibility API
  • ✅ Modern Playwright Usage: The TUnit.Playwright module (/home/runner/work/TUnit/TUnit/TUnit.Playwright/) uses modern Playwright APIs:
    • Microsoft.Playwright.Playwright.CreateAsync()
    • Standard browser/context/page lifecycle management
    • Playwright assertions (Microsoft.Playwright.Assertions.Expect)

Security Considerations

  • Safe Update: This is a minor version bump (1.56.0 → 1.57.0) with no known security vulnerabilities
  • Chrome for Testing: The switch from Chromium to Chrome for Testing provides better stability and consistency
  • No API Surface Changes: No new security-related APIs or changes that would affect the security posture

Performance Considerations

  • Browser Engine Improvement: Switch to Chrome for Testing may provide better performance and stability
  • No Performance Regression Risk: The existing code in TUnit.Playwright doesn't use any deprecated patterns
  • Efficient Resource Management: The existing code properly disposes of Playwright resources in cleanup hooks

Test Coverage Assessment

  • Existing Coverage: The TUnit.Playwright module has proper setup/teardown lifecycle management
  • Integration Points: All Playwright integrations are through the TUnit.Playwright wrapper classes
  • No Test Updates Needed: Since no deprecated APIs are used, existing tests should continue to work

📋 New Features Available (Optional Adoption)

  1. Worker.Console event - Could be useful for debugging worker-related tests
  2. Locator.Description - Could enhance test readability and debugging
  3. Steps option in click/drag actions - Could provide more realistic user interactions

🔧 Files Analyzed

  • /home/runner/work/TUnit/TUnit/Directory.Packages.props - Version update
  • /home/runner/work/TUnit/TUnit/TUnit.Playwright/PlaywrightTest.cs - Core Playwright wrapper
  • /home/runner/work/TUnit/TUnit/TUnit.Playwright/PageTest.cs - Page-level testing
  • /home/runner/work/TUnit/TUnit/TUnit.Playwright/BrowserTest.cs - Browser-level testing
  • /home/runner/work/TUnit/TUnit/TUnit.Playwright/ContextTest.cs - Context-level testing

Recommendation

APPROVE - This is a safe, beneficial update with no breaking changes affecting the codebase. The dependency update follows best practices and the project's Playwright integration uses modern, supported APIs.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Microsoft.Playwright dependency from version 1.56.0 to 1.57.0, incorporating a minor version update that includes new APIs and a switch from Chromium to Chrome for Testing builds.

Key Changes:

  • Updates Microsoft.Playwright package version from 1.56.0 to 1.57.0
  • No code changes required as the codebase doesn't use any deprecated APIs (specifically Page.Accessibility which was removed in this version)

This was referenced Dec 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file MINOR renovate-bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants