What's new in Playwright v1.46: Client certificates, only changed, ui mode

[@rostyslavznachenko7472]

Only changed test using branch and usages are amazing features that allows you to do all kinds of funky stuff, like verifying your tests in the PRs. In my projects, I always implemented that myself, and now it is available out-of-the-box-amazing!

[@thelastbreaths]

appreciate as always playwright because this is a real OG 🔥🤘 kindly make it more flexible like we can important extension directly like google chrome hope it will be appreciated thanks & take 💕

[@jaysonlabarrete9121]

I love playwright and the new updates!

[@lequangtan2106]

Really great series. Not sure if we can something like this but in java or this also can be applied too

[@Playwrightdev]

Client Certificates and Trace Viewer updates are available in Java too. Happy testing!

[@Sunils_Creations]

love Playwright

[@oleksiidmytriiev5390]

Great update. Thank you!

[@kasikcz]

7:14 this reminds me of Night time, Day time bird video :D

[@muhammedozdogan5133]

In the client certificate selection I don't need to specify any certificate I just need to click on "Cancel" button is it possible with Playwright?

[@kirankumar-co9wf]

in the case I have multiple environments and pass it as argument launches and closes ?

[@Demios93]

do you plan to add a name filter for requests in a trace viewer in the Network tab? Also, a filter for actions as well? Like only errors

[@jozefszymala3764]

❤ yep searching for request currently is really annoying, filters would be so helpful something similar do dev tools

[@Playwrightdev]

great idea. can you file a feature request on GitHub

[@Norfeldt]

Wondering if you can run only-changed in a watch mode?

[@Playwrightdev]

Not right now. Do you mind filing a feature request on GitHub? thank you!

[@duongpisal3175]

Really cool

[@AppOffers]

When are you planning to add support to proxy and client certificates together?

[@Playwrightdev]

Please file an issue on GitHub - depending on the demand, we'll prioritise it, thank you!

[@taxet]

I really like the only changed feature, but it doesn't seem to take into account any of the dependencies of the project? Like for example when I have a project for tests and it has a dependency on a setup project that handles login so I don't need to login on each test fixture, if I make a change on one of the tests, it just tries to run the test but doesn't run the setup first and the tests fail because of that. Means I can't really make use of this as it is, but still a neat feature.

[@Playwrightdev]

This should be fixed in v1.46.1 - please file a bug on GitHub if it still doesn't work for you, thanks!

[@taxet]

@@Playwrightdev Yeah now it works, good work all! 👍

[@joaodias1023]

Hello :) Nice new additions, keep up! By the way, any news or updates regarding component testing with playwright? Seems like it has been stale for a couple of months now. Thanks! :)

[@Playwrightdev]

If you have any feedback on it, please file an issue on GitHub! We love to hear component testing feedback which is necessary for us to move this feature forward.

[@dorhaalex5354]

Hello Since latest VS Code update the Playwright extension is not working anymore The extension is not able to find the tests, before VS Code update was ok, now is not working Are you planning to fix this?

[@Playwrightdev]

everything should work as expected. if you are still having problems please file an issue on GitHub so the team can look into it

[@harshadabagane1505]

Is it supporting only .pem extension or will it support.pfx certificate also.?

[@Playwrightdev]

it supports both, pfx and pem format. See here: playwright.dev/docs/api/class-testoptions#test-options-client-certificates

[@geoffreycollins6627]

It seems like the new router fixture hasn't received enough attention in the demo

[@Playwrightdev]

you are right. we couldn't fit everything in unfortunately. let us know what you think of this feature

[@geoffreycollins6627]

@@Playwrightdev is there anything in the playwright doc?

[@InsightsHub]

Playwright is good when your project is not heavy or complex. I am seeing a lot of issues with playwright APIs and in some cases Playwright APIs are flaky. You guys are adding too much features but none of them are matured yet. Better focus on whatever features you guys have built and make it more stable. Start with Intercepting requests and timeout management for long running tests.

[@Playwrightdev]

please file issues on Github :)

[@UserUnkown-do1ji]

I started using Playwright API in 100s of test cases where we create our data using the API instead of UI, and so far it does good job, and saved a lot of time spent on UI just to create the data used in the test.

[@sergtimosh]

Never used less flaky test tool then playwright. After selenium, cypress, puppeteer path, it’s like a breath of the fresh air by ease of use and flaky proofing, especially on the large projects

[@michaelhicks3745]

We have hundreds of tests that use Playwright's request API and I've never seen any issues with them. The only issues I've seen are usually user errors and folks forgetting to add await's