-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🎅 Playwright Santa 2025 🛷 #33955
Comments
this #22791 |
Fix the bugs, bro. |
Projects and UI Mode improvement to make working with multiple browser/scopes/environments configurations easy: |
arm64 support for the snapdragon-based ms surface tablets/latops |
The removal of the experimental flag on component testing🤞 |
Full support for Component testing with examples and documentation. Help channel in discord meant only for component testing. |
Easy extensibility to add support for different apps which may be hosting Chromium or WebView2 web views. Our use case is a Microsoft Office app extension which runs in the Office app and displays content in the taskpane using web view. Simillary to Android support where we can run Anroid app and connect to its web view, we would like to create integration between Playwright and the Office apps. This would allow us to test if the actions in the web view had effect on the document in the Office app. We know how to implement the Office app COM addins would drive the automation in a similar way the DevTools protocol does. It would expose the application model and data to PW tests. We are stuggling with integrating this to Playwright seamlessly though. |
#26507 |
In vscode, I'd like the ability to add timing instrumentation to our own packages so that when I'm running tests, I can tell where playwright is spending its time. When the test setup process takes time, it's important to know how long it takes so that we don't end up extending test timeouts to unreasonable numbers. Thx! |
Support for mobile and desktop 💃 |
It would be nice if you could enrich the default HTML test reports with new options like pie charts etc. These reports are shown also to the manager layer, otherwise they only see a list of lines. Also to add native app testing, for instance, by using clouds based on appium. At the end, E2E testing requires most of the time web, api, app & db steps combined to validate a customer journey. If we cannot do some "parts" (e.g., app), Playwright cannot validate the whole customer journey, there is no workaround for this. Our companies pay us as testers to cover & protect those flows, test cases are just means to do that, which is the real goal. |
In 2025 I wish Playwright will integrate some AI stuff to help with writing and debugging e2e tests 🎄🎄🎄 |
I wish a new AI locator function getByDescription(), where I can enter something like Button used to submit my form, labelled as Sign in. During run-time, the locator would connect to an AI service, which will determine in real-time the best locator for this human description based on the current page DOM of the system under test. |
I would like to see this one: |
https://github.com/empirical-run/appwright I haven't tried it yet, but it looks promising. |
#22937 -- This is blocking to use parallel runs :( . |
#23827 definitely not the most urgent feature but life would be better with it |
I think this fits with the holiday spirit: I would like for Playwright to make the "View Trace" button more prominent in the HTML report. As it stands, the test title link, the filename link and the video link all take the user to the At work, we had to point folks to the trace viewer multiple times, because it is easy to miss. This is a bit of a shame, because the trace viewer is the best part of Playwright, from my perspective 😅 This became annoying enough that we started overwriting the HTML reports and injecting some CSS to brighten the trace viewer button up ✨ It's just some CSS targeting (I can file an issue if you think this makes sense 😇) |
Report / Table View:
Trace View Related:
|
#28542 await this.page.getByText(deviceName).waitFor({ timeout: 200 }).catch(() => { }); |
Integration with Azure test plan. |
Please help with this: |
Accessing the request object through the response objects to get the method and headers. This is really good for debugging purposes We utilize "rest clients" and there if we get back a non 2xx response we try to parse info from the response and print it to the log. Sometimes we have the same endpoints for different methods and it hard to know with one it is. To over come this I have a dirt hack to find the name of the calling method, that looks something like this: |
Be able to use hyperlinks in annotations in html report. Example:
|
Add tests with update snapshots to the -onlyChaged test run 🫶 |
Adding some advanced HAR configuration would be cool (see #21405). Also, seems like "minimal" mode doesn't work well. Also, it could be nice if |
I have three ideas that I think would be super helpful:
|
Want to have the ability run describes in serial mode but tests inside in default mode like for parallel
|
I'd also love |
Playwright Grid like Selenium Grid. |
an integrated, no-nonsense, reliable and simple to use coverage gathering/reporting mechanism. keep up the excellent work and merry xmas people! |
Native BDD support please |
self-cure |
Would be great to get playwright maintainers back on the table to discuss improvements of the test runner... |
Would also love to see custom asymmetric matchers to be fully supported... |
Option to extend the HTML reporter or easily create custom UI reporter using some common functionality with HTML reporter like iterating steps and generating the code, etc. |
Considering a typical workflow comprises using codegen to generate (bad) selectors for various parts of a page and then jumping into an editor to fine-tune all the selectors to make them more robust, it would be nice if the codegen macro tool itself presented alternatives to choose from when building locator paths. |
Appium like support for Mobile Native App automation. |
Running non-patched Firefox builds with BiDi support :) Also should fix the Firefox extension issue |
Component Testing for Angular |
Yes, please!!! |
Pretty please! |
Thank you for your requests! Santa has noted all your requests and returned to the North Pole to decide which ones to do first! Happy New Year! |
this #31823 |
Add ability to work with desktop /mobile apps. |
neovim plugin for Playwright ;) :P |
Rich logic experience around when to capture response bodies in a HAR file. Example: Status Code I want the response body for a static resource request when the status code is >= 400 URL Reg Ex The AUT may have XHR requests that are mundane but large and i am not interested in them, but some XHR are crucial and i want to always capture response bodies I am going to implement this post-processing but to have this defined before the test starts would be awesome |
Playwrigh Pytest specific ambassadors and release note presentations |
Vote for Component Testing with Angular |
Please recognize the semantic difference between |
Tell us what you'd like to see in Playwright in the next year!
The text was updated successfully, but these errors were encountered: