I have tried using their testing skills, and it got close to my current set of test cases. Curious to see if anyone has tried out any other skills or the Android CLI?
Tried using their testing skills, and it got close to my current set of test cases. Curious to see if anyone has tried out any other skills or the Android CLI?
Tried using their testing skills, and it got close to my current set of test cases. Curious to see if anyone has tried out any other skills or the Android CLI?
I have tried using their testing skills, and it got close to my current set of test cases. Curious to see if anyone has tried out any other skills or the Android CLI?
I had started using Claude code, maybe 2 months ago, mostly to generate test cases and write automation scripts.
However few other QA teams in my org are way ahead of me. They have built custom agents, written custom skills, and wired up MCPs so they barely have to leave the IDE. Helps them right from dev ticket → test cases → scripts → fixing failures, all in one place.
It has left me wondering where I actually stand, and more so where everyone else really is in their AI journey. If you're using coding agents (Copilot, Cursor, Claude Code) for testing, where would you honestly put yourself?
I had started using Claude code, maybe 2 months ago, mostly to generate test cases and write automation scripts, and can see it has already helped my case to be faster.
However few other QA teams in my org are way ahead of me. They have built custom agents, written custom skills, and wired up MCPs so they barely have to leave the IDE. Solves right from requirements → test cases → scripts → fixing failures happens in one place.
It has left me wondering where I actually stand, and more so where everyone else really is in their AI journey, not the LinkedIn hype version, but the real one. If you're using coding agents (Copilot, Cursor, Claude Code) for testing, where would you honestly put yourself?
Fellow automation engineers!
I've been using Claude Code for my testing tasks lately, mostly script authoring. Works well enough for me.
Now my org wants me to scale this into a end-to-end AI workflow in the IDE. The vision: generate test cases from PRDs → use them to author scripts → have AI pull failures from the CI pipeline and auto-fix the scripts. They want us SDETs to figure out with MCPs, custom skills, and in-house agents if needed.
Honestly, it looks scary from where I'm standing - just started this journey 2 weeks ago.
So I'm hoping to hear from people who've actually done this (or are actively building it). A few specific things I'd love to know:
1..Which coding agent are you using — Copilot, Cursor, or Claude Code?
2.How did you build the setup — solo, with other SDETs in your org, or did developers pitch in?
3.Roughly how long did it take to get something usable?
Just trying to learn from the community to build this faster
We are just getting started with accessibility testing and trying to figure out what tools to use. Would love to know what your team uses day-to-day before I go down a rabbit-hole of docs and trials. What has worked for you?
We are just getting started with accessibility testing and trying to figure out what tools to use. Would love to know what your team uses day-to-day before I go down a rabbit-hole of docs and trials. What has worked for you?
We have been doing accessibility testing for a year now but recently due to a change in internal data management policies we are evaluating providers who offer on-premise hosting options for accessibility testing (mainly because we handle PII).
Curious to see if anyone else has tried this? If yes, which providers do you use?
We have been doing accessibility testing for a year now but recently due to a change in internal data management policies we are evaluating providers who offer on-premise hosting options for accessibility testing (mainly because we handle PII).
Curious to see if anyone else has tried this? If yes, which providers do you use?
We have been doing accessibility testing for a year now but recently due to a change in internal data management policies we are evaluating providers who offer on-premise hosting options for accessibility testing (mainly because we handle PII).
Curious to see if anyone else has tried this? If yes, which providers do you use?
We have been doing accessibility testing for a year now but recently due to a change in internal data management policies we are evaluating providers who offer on-premise hosting options for accessibility testing (mainly because we handle PII).
Curious to see if anyone else has tried this? If yes, which providers do you use?
Been doing web testing for years. Just took on mobile for the same product - realized its a different world
Every sprint, same feature scope, but mobile testing seems to take longer vs web. Wondering if this is everyone's experience or if its that we're still finding our feet.
For those of you doing/ have done both mobile and web testing - where do you actually feel there is more time spent in mobile vs web testing?
I’ve noticed that production monitoring for the main site (landings, blogs, etc.) usually falls into a weird gray area, unlike the actual software product.
Curious how your org handles this
I’ve noticed that production monitoring for the main site (landings, blogs, etc.) usually falls into a weird gray area, unlike the actual software product.
Curious how your org handles this.
Been doing web testing for years. Just took on mobile for the same product - realized its a different world
Every sprint, same feature scope, but mobile testing seems to take longer vs web. Wondering if this is everyone's experience or if its that we're still finding our feet.
For those of you doing/ have done both mobile and web testing - where do you actually feel there is more time spent in mobile vs web for a similar feature?