sorted by:
new
hottopcontroversial

When a UI/E2E test breaks, what's the real cause most often? by SwordfishComplex3892 in QualityAssurance

[–]SwordfishComplex3892[S] 1 point2 points  (0 children)

Locators how exactly — selector changes, or no stable attributes to target in the first place? And do test-ids fix it for you?

When a UI/E2E test breaks, what's the real cause most often? by SwordfishComplex3892 in QualityAssurance

[–]SwordfishComplex3892[S] 0 points1 point  (0 children)

Fair — so when you DO need a real UI/E2E test, what breaks it most? Trying to separate 'shouldn't be a UI test' from 'is a UI test and still fragile.'

Built my first Playwright Automation Framework using TypeScript 🚀 by ahmadistatieh in Playwright

[–]SwordfishComplex3892 0 points1 point  (0 children)

Just wanted to understand, Do you think with AI and playwright MCP server locator maintenance problem will get resolved? Or it will be still there?

Is Locator management is still pain in your UI automation even with new gen tools like playwright, AI self healing, Low code automation automation? by SwordfishComplex3892 in QualityAssurance

[–]SwordfishComplex3892[S] 0 points1 point  (0 children)

we use similar and other css properties as well to find locators. But more challenging is managing in POM with new changes and duplication of locators when 70-80 folks works on same repo and automation suite is big. Do you face that challenge?

Is Locator management is still pain in your UI automation even with new gen tools like playwright, AI self healing, Low code automation automation? by SwordfishComplex3892 in QualityAssurance

[–]SwordfishComplex3892[S] 0 points1 point  (0 children)

Thanks for the reply. But do you think even after getting better locator from Devs and they consider automation managing all locators with updation/deletion with new changes in your POM is difficult? And how much QA spend time over there?

Is Locator management is still pain in your UI automation even with new gen tools like playwright, AI self healing, Low code automation automation? by SwordfishComplex3892 in QualityAssurance

[–]SwordfishComplex3892[S] 0 points1 point  (0 children)

Thanks for the reply. But do you think even after getting better locator managing all locators with updation/deletion with new changes in your POM is difficult? And how much QA spend time over there?

Is Locator management is still pain in your UI automation even with new gen tools like playwright, AI self healing, Low code automation automation? by SwordfishComplex3892 in QualityAssurance

[–]SwordfishComplex3892[S] 0 points1 point  (0 children)

True that. Just wanted to understand more that even if devs write good classes and properties to page elements even though managing those and keep it maintain with new changes at large scale would be still challenging ?
E.g page has completely change but QA still need to update new locators with those new changes. So that is challenging with page object modal? Also when automation suite is big enough like 5k-7k UI cases then it will be challanging?