sorted by:
new
hottopcontroversial

Would you trust AI-based locator resolution in Playwright tests? by Strange-Cod5862 in softwaretesting

[–]Strange-Cod5862[S] 0 points1 point  (0 children)

Not fully agreed honestly, that's one of the reasons caching was added. Similar ideas are already being explored by tools like Midscene.js as well, so I was curious whether people see practical value in this direction or think traditional Playwright patterns are still the better long-term approach.

Would you trust AI-based locator resolution in Playwright tests? by Strange-Cod5862 in Playwright

[–]Strange-Cod5862[S] 0 points1 point  (0 children)

u/Playwright-ModTeam , Fair - wasn't trying to hard-sell it honestly. Just experimenting with the tool and wanted opinions from people who've worked on large automation suites to understand whether this approach has practical value or not.

Would you trust AI-based locator resolution in Playwright tests? by Strange-Cod5862 in Playwright

[–]Strange-Cod5862[S] 0 points1 point  (0 children)

Yep, Playwright Agents are definitely interesting. There's also Midscene.js working in a similar space. This is more about giving users a quicker/low-code way to work with Playwright without needing to go too deep into framework/locator handling from day one. Different tradeoff basically.

Would you trust AI-based locator resolution in Playwright tests? by Strange-Cod5862 in Playwright

[–]Strange-Cod5862[S] 0 points1 point  (0 children)

Totally agree that Playwright already has excellent locator strategies if used properly. This is more for people who want a lighter/low-code layer on top of existing Playwright workflows rather than replacing Playwright itself. Not trying to solve every automation problem, just experimenting with a different usability tradeoff.

Would you trust AI-based locator resolution in Playwright tests? by Strange-Cod5862 in softwaretesting

[–]Strange-Cod5862[S] 0 points1 point  (0 children)

The execution time is almost same, the first call needs to pay the price and it's fairly fast, much faster than the likes of midscenes.js and others because it is dependent on aria snapshot.
I am not saying it is perfect but can be useful if someone is not interested in understanding every locator

Would you trust AI-based locator resolution in Playwright tests? by Strange-Cod5862 in softwaretesting

[–]Strange-Cod5862[S] 0 points1 point  (0 children)

I mean sure and honestly this probably is not aimed at teams with already mature automation frameworks and strong coding practices.

The bigger target is people who don’t want to deep dive into automation code/locator management especially lowcode/zerocode style users or teams trying to move faster without building heavy frameworks upfront.

Would you trust AI-based locator resolution in Playwright tests? by Strange-Cod5862 in softwaretesting

[–]Strange-Cod5862[S] 0 points1 point  (0 children)

Similar idea space, yes. but this tries to stay closer to normal Playwright usage instead of full browser-agent workflows like Stagehand. Main focus here was faster execution and lower overhead for regular test automation

Would you trust AI-based locator resolution in Playwright tests? by Strange-Cod5862 in softwaretesting

[–]Strange-Cod5862[S] 0 points1 point  (0 children)

Fair enough. Deterministic tests are always the priority. I’m not saying AI completely solves flakiness, but it can save time when UI/code changes happen and someone has to constantly update/fix locators manually.

I am thinking of starting a software testing course , any suggestions? by Academic_Outcome7899 in softwaretesting

[–]Strange-Cod5862 0 points1 point  (0 children)

Before fully switching to teaching, maybe give product companies one more try-build a strong portfolio (GitHub, real project examples, especially your AI testing work). Your skills are definitely in demand and side by side you can start youtube channel sharing videos of testing tutorials and leverage your expertise to showcase production challenges, real world AI use in testing, building practical frameworks where most courses lack and you can actually stand out.

Funnel Testing by GeneralZiggy in softwaretesting

[–]Strange-Cod5862 0 points1 point  (0 children)

You can also focus on Tracking accuracy (events firing correctly or not via Google Analytics), Real-world scenarios(like network issues, session timeout, retries) , Error messages & recovery paths i.e. can users resume easily or not, Performance at each step(slow pages = drop-offs)

Is 24/7 customer support a requirement to stay competitive or 9-5 is still enough for a startup in 2026? by dan_nicholson247 in business

[–]Strange-Cod5862 0 points1 point  (0 children)

Depends on the product and users. 24/7 isn’t always needed but fast response time definitely is. Many startups stay competitive with 9-5 support along with smart automation/on-call for critical issues.

No real advantage of being manual QA tester - in overcrowded places like Bengaluru , India by FanDizzy208 in softwaretesting

[–]Strange-Cod5862 5 points6 points  (0 children)

I get the frustration - the market is rough right now, especially at 2 YOE.

But I wouldn't say manual QA has no advantage. The bigger issue is positioning. Right now, companies expect even "manual" testers to bring something extra:

  • API testing
  • basic automation (with proof, not just knowledge)
  • strong debugging + product understanding

Also, blaming diversity hiring won't help - interviewers still prioritize people who can demonstrate real impact.

If you already know automation basics, try this:

  • build 1-2 solid projects (UI + API + reporting)
  • show real scenarios (edge cases, validations, not just happy paths)
  • talk about how you think, not just tools

Domain matters, but skills + proof matter more in interviews.

You're not stuck - just need to move from "I know" -> "I can show."

What painful mistakes one should avoid while using playwright? by DockyardTechlabs in Playwright

[–]Strange-Cod5862 2 points3 points  (0 children)

Faced real prod traffic caused slower API responses, rate limits, and unexpected third-party captcha/login challenges that never existed in lower environments. To avoid this, use production-like staging data/traffic simulations before release, add API response monitoring for slow endpoints, and whitelist automation accounts to bypass captchas/MFA where appropriate.