Skip to content
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

Closed
pavelfeldman opened this issue Dec 11, 2024 · 126 comments
Closed

🎅 Playwright Santa 2025 🛷 #33955

pavelfeldman opened this issue Dec 11, 2024 · 126 comments

Comments

@pavelfeldman
Copy link
Member

pavelfeldman commented Dec 11, 2024

Tell us what you'd like to see in Playwright in the next year!

@pavelfeldman pavelfeldman changed the title Playwright Santa 2025 🎅 Playwright Santa 2025 🛷 Dec 11, 2024
@Smrtnyk
Copy link

Smrtnyk commented Dec 11, 2024

this #22791

@Bilge
Copy link

Bilge commented Dec 11, 2024

Fix the bugs, bro.

@jaktestowac
Copy link
Contributor

Projects and UI Mode improvement to make working with multiple browser/scopes/environments configurations easy:
#23084

@AronStankovics
Copy link

arm64 support for the snapdragon-based ms surface tablets/latops

@sand4rt
Copy link
Collaborator

sand4rt commented Dec 11, 2024

The removal of the experimental flag on component testing🤞

@scott-au
Copy link

[Feature] automatically handle frames

@Manjunath224
Copy link

Full support for Component testing with examples and documentation.

Help channel in discord meant only for component testing.

@chensce
Copy link

chensce commented Dec 12, 2024

#23700

@jozefizso
Copy link
Contributor

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.

@MindaugasMateika
Copy link
Contributor

#26507
to scale testing on our own without relying on CI resources

@richmar10
Copy link

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!

@luisecm
Copy link

luisecm commented Dec 12, 2024

Support for mobile and desktop 💃

@gjmargallo
Copy link

gjmargallo commented Dec 13, 2024

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.

@vitalets
Copy link
Contributor

In 2025 I wish Playwright will integrate some AI stuff to help with writing and debugging e2e tests 🎄🎄🎄

@gjmargallo
Copy link

gjmargallo commented Dec 13, 2024

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.

@erayerdin
Copy link

#11164 is definitely a missing feature. Firebase utilizes IndexedDB (for some weird reason) in order to save its authentication state. Working with it is a nightmare. It causes a lot of headaches like #34000.

@Hacktivist668
Copy link

#2903

@marcusNumminen
Copy link
Contributor

I would like to see this one:
#23354
(make it possible to run the retries in the end of the run)

@apatelia
Copy link

Support for mobile and desktop 💃

Just kidding, but I wish there is something as good as playwright for desktop/mobile

https://github.com/empirical-run/appwright

I haven't tried it yet, but it looks promising.

@kristaps-aksjonovs
Copy link

kristaps-aksjonovs commented Dec 16, 2024

#22937 -- This is blocking to use parallel runs :( .
Would be great to use full power of Playwright in pipeline

@StanislavGrishaev
Copy link
Contributor

StanislavGrishaev commented Dec 16, 2024

#23827 definitely not the most urgent feature but life would be better with it

@fpapado
Copy link

fpapado commented Dec 16, 2024

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 #?testId page, but only the tiny "trace viewer" (rectangle sliced in three parts) icon link takes them to the trace viewer. There is no visible label for those icon links.

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 a[href^="trace/"] and related parts (svg and ::after), but it would be cool to see something built-in, or first-class extension point to the viewer.

(I can file an issue if you think this makes sense 😇)

Image
Image

@orizens
Copy link

orizens commented Dec 16, 2024

Report / Table View:

  1. memorize collapsed tests (idea - via search query)

Trace View Related:

  1. filter / search network tab
  2. highlight related network rows per selected action (in the Actions panel)
  3. highlight / indicate waitForResponse in network tab
  4. show "fill" values in Actions (locator now does)

@terradek
Copy link

#28542
Currently I use this

await this.page.getByText(deviceName).waitFor({ timeout: 200 }).catch(() => { });

@hardeep-qa
Copy link

Integration with Azure test plan.

@TusharAnandTR
Copy link

@marcusNumminen
Copy link
Contributor

Accessing the request object through the response objects to get the method and headers. This is really good for debugging purposes

#16239

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:
const callerName = new Error().stack.split('at ')[2].split(' ')[0];

@quldude
Copy link

quldude commented Dec 18, 2024

Be able to use hyperlinks in annotations in html report. Example:

Bug: [<a href="https://somelink" target="_blank">ABC-1234</a>] Bug title.

@SofianeH1
Copy link

SofianeH1 commented Dec 23, 2024

Add tests with update snapshots to the -onlyChaged test run 🫶

@NoamGaash
Copy link
Contributor

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 page.clock had an API to freeze the datetime, and resolve timeouts imminently. It would be useful for tooltips and autocomplete components that has denounce in the entrance animation

@marnandr
Copy link

I have three ideas that I think would be super helpful:

  1. Official support for Azure Test Plans ⚗ reporting ([Feature] Playwright integration with Azure DevOps Test Plans #14839).
  2. Improved support for Azure Pipelines 🚀 (I will do my best to contribute to the documentation).
  3. Support for print dialog events 🖨 as page.waitForEvent() ([Feature] Listen for print dialog #6543).

@lkasianenko-splash
Copy link

lkasianenko-splash commented Dec 24, 2024

Want to have the ability run describes in serial mode but tests inside in default mode like for parallel

test.describe.configure({ mode: 'serial' });

test.describe('A, runs in parallel with B', () => {
  test.describe.configure({ mode: 'default' });
  test('in order A1', async ({ }) => { expect(true).toBe(true); });
});

test.describe('B, runs in parallel with A', () => {
  test.describe.configure({ mode: 'default' });
  test('in order B1', async ({ }) => { expect(true).toBe(false); });
  test('in order B2', async ({ }) => { expect(true).toBe(true); });
});

@cctui-dev
Copy link

I'd also love test.step.skip() to be implemented :)

@perjerz
Copy link

perjerz commented Dec 25, 2024

Playwright Grid like Selenium Grid.

@olaf-k
Copy link

olaf-k commented Dec 25, 2024

an integrated, no-nonsense, reliable and simple to use coverage gathering/reporting mechanism. keep up the excellent work and merry xmas people!

@ramam-v
Copy link

ramam-v commented Dec 25, 2024

Native BDD support please

@tdhanjun
Copy link

self-cure

@muhqu
Copy link
Contributor

muhqu commented Dec 26, 2024

Would be great to get playwright maintainers back on the table to discuss improvements of the test runner...

@muhqu
Copy link
Contributor

muhqu commented Dec 26, 2024

Would also love to see custom asymmetric matchers to be fully supported...

@yonatanai
Copy link

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.

@Bilge
Copy link

Bilge commented Jan 1, 2025

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.

@Wish-Infinite
Copy link

Appium like support for Mobile Native App automation.

@Jaakkonen
Copy link

Running non-patched Firefox builds with BiDi support :) Also should fix the Firefox extension issue

@AlaaEl-DinAhmed
Copy link

Component Testing for Angular

@fMoro1999
Copy link

Component Testing for Angular

Yes, please!!!

@shilCode
Copy link

shilCode commented Jan 5, 2025

Component Testing for Angular

Pretty please!

@pavelfeldman
Copy link
Member Author

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!

@wangdatu
Copy link

wangdatu commented Jan 8, 2025

this #31823

@lvrub
Copy link

lvrub commented Jan 9, 2025

Add ability to work with desktop /mobile apps.

@radekBednarik
Copy link

neovim plugin for Playwright ;) :P

@robbiewareham
Copy link

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

@mandras73
Copy link

Playwrigh Pytest specific ambassadors and release note presentations

@dylannnn
Copy link

Vote for Component Testing with Angular

@TomasHubelbauer
Copy link
Contributor

Please recognize the semantic difference between test.todo and test.fixme and introduce the former (there are already several closed issues for this which could be reopened) or codify the team's view they aren't semantically different to them (which I don't agree with, but it's ultimately not my call) by introducing a test.todo alias for test.fixme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests