search

microsoft / playwright

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
https://playwright.dev
Apache License 2.0
66.34k stars 3.63k forks source link

[Feature]Self-healing #10872

Closed chenshuichao closed 2 years ago

chenshuichao commented 2 years ago

ref: https://github.com/healenium/healenium-web

pavelfeldman commented 2 years ago

Self-healing is not currently on the roadmap. It is important for our customers to know if the test failed or passed.

SimonJohnAde commented 1 year ago

I would like to add my vote to Self-Healing of scripts. As the number of scripts scale, maintenance becomes a factor and I aggree that customers want to know if a test passed or failed, but I imagine they want to be informed of the important failure, not minor changes to id's on dynamic elements for example.

I must emphasize the dynamic nature here. These are not so uncommon and would 'fail' a regression test when really it could be 'self-healed'. For Web UI's that are more dynamically built, the script maintenance becomes a night-mare.

Our company recently compared PlayWright to another product and it was this key-feature that swung the vote to not use PlayWright. Which is why I am raising it here as I believe PlayWright is a fantasic product and would.

Please reconsider.

miguelofbc commented 1 year ago

@pavelfeldman IMHO the users should be able to decide if they want to enable that feature or not. Also, the self healing cases could be raised for each run and with that, the user could update the code in order to reflect the element changes.

Coding-Means-Always-Learning commented 1 year ago

I totally agree this feature should be looked into by playwright. The concept of shift left and automate first means automation testers do not need to worry about minor selector getting updated by the developers during application build phase.

Many of new licensed automation tool report to the users which selectors have changed and if they wish to update them for the next run. By having this we are ensuring a large pack of end to end tests are not failing due to change in selectors and also provides an insight what has changed. It is upto the users to decided whether they want to report the selector difference

Could this be re-opened and considered a future feature

IuliaSacelean commented 10 months ago

Still not reconsidered? :(

mubashirbhat commented 7 months ago

Maintenance is one of the important factor for Automation suite . Self healing is one such segment which reduces a good amount of time in that areas , which will help to focus on failures that matter the most . I am in process of making a decision to shift away from Selenium to Playwright , but if Selfhealing is not an option right now , i would need to better go back to the drawing board .

Any idea if Self healing is in consideration .

AnubisRooster commented 7 months ago

Agree with all previous comments - self healing is a must-have feature. Please prioritize this for your roadmap.

jamesmortensen commented 2 months ago

It's not the same as Healenium, but this QA Automation Youtuber has a solution that may help those of you choosing to use selectors: https://www.youtube.com/watch?v=33arpwEWmdc.

SimonJohnAde commented 2 months ago

Thanks for sharing @jamesmortensen Think it has a lot of value in the right direction.

priyankkumar218 commented 3 days ago

Has this been added to the roadmap yet? Imo, it will make Playwright tests much more scalable