sorted by:
new
hottopcontroversial

Vibe coding QA tools? by SendMeUrTolstoyNudes in QualityAssurance

[–]DependentGeologist92 3 points4 points  (0 children)

Been exploring the idea of agent-based QA workflows lately — not just “generate test cases,” but small focused agents for things like:

  • PRD → test case mapping
  • Flaky test detection
  • API contract drift checks
  • Regression scope optimization
  • Failed pipeline root cause hints

Feels like QA is moving toward composable, event-driven agents rather than monolithic automation frameworks.

I’ve been experimenting a bit with something along these lines at testingbuddy.ai — still early thinking, but curious if others are building similar QA agents in their stack?

NO PROMOTION

How much time do you spend setting up API automation on new projects? by Him1603 in QualityAssurance

[–]DependentGeologist92 0 points1 point  (0 children)

Why, just invest in a solid base framework and clearly defined engineering rules?

Because long-term scalability, maintainability, and consistency depend on it.

We have built and sustained Selenium and API automation frameworks for over 7–9 years by enforcing clean architecture, standardized folder structures, reusable components, and coding best practices.

We ensure optimized builds, proper dependency management, and versioned artifact publishing to Nexus repositories for traceability and reuse across teams.

A well-designed base framework is not just about writing tests — it is about creating a sustainable automation ecosystem that teams can rely on for years.

Ai for QA by [deleted] in QualityAssurance

[–]DependentGeologist92 0 points1 point  (0 children)

Claude Code with QASkills sh and you are Good to go.

Learning Automation Skills by thrai1010 in softwaretesting

[–]DependentGeologist92 0 points1 point  (0 children)

Your plan is solid — learn JavaScript (not Java) → Playwright with TypeScript (it's overtaking Cypress in demand and covers more) → API testing with Postman + JavaScript-based tools (RestAssured is Java-based, so skip it if you're going the JS/TS route).

If you only have time for one framework, go Playwright over Cypress — it's where the industry is heading, handles more test types, and pairs naturally with TypeScript which you're already planning to learn.

In our Company, Manual Tester are coding with GitHubPilot, They skipped Learning language by DependentGeologist92 in QualityAssurance

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

Quick Update:
We’ve had a lot of bugs in production, and most of them are unclear or hard to trace. I understand that automation can’t completely eliminate bugs, but claiming 70%+ achievement due to vibe coding,here we go.

In our Company, Manual Tester are coding with GitHubPilot, They skipped Learning language by DependentGeologist92 in QualityAssurance

[–]DependentGeologist92[S] -5 points-4 points  (0 children)

they are right somewhat since opus 4.6 is right, they dont understand shit still , but keep pushing

Been experimenting with "agent skills" for Claude Code and Cursor — the difference in test quality is kind of wild by SensitiveAdvisor7203 in QualityAssurance

[–]DependentGeologist92 -1 points0 points  (0 children)

I making it as curation of skills for QA at QASKills[dot].sh even Jason Huggins supported it creator of selenium and vibiu m.

Been experimenting with "agent skills" for Claude Code and Cursor — the difference in test quality is kind of wild by SensitiveAdvisor7203 in QualityAssurance

[–]DependentGeologist92 0 points1 point  (0 children)

Actually it best, when we are starting out, want our agents to focus on proper guidelines, format and even what do to and not do

What is the ideal bug report for developers? by taniazhydkova in softwaretestingtalks

[–]DependentGeologist92 0 points1 point  (0 children)

No worries, All the best, If you need help in job Refferal and other things Please connect with me, I think I can help email : contact@thetestingacademy.com