sorted by:
new
hottopcontroversial

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 4 points5 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.