
I lean on Claude for the parts of QA that aren't writing code. We keep a Project for each client app with the requirement docs and test notes, so when I ask for test scenarios for a new story it already knows how the module works and what we covered last sprint. My favourite setup is the ClickUp connector combined with a skill set up for our bug report format. I describe what I found and it creates the bug as a subtask under the right task, with the title, severity and steps already in our template. It's also good at reading a long requirement document and pointing out gaps or contradictions before development starts, which saves a lot of back and forth later. Review collected by and hosted on G2.com.
The usage limits are the biggest annoyance. On days when I'm going through a lot of documents or a long chat, I hit the cap and have to wait or switch to something else. Answers can also run longer than I need, so I often add 'keep it short' to my prompts. It occasionally gets a detail from a long document wrong, so anything that goes to a client still gets checked by me first. It also can't generate images, which would be handy for quick annotated screenshots in bug reports. Review collected by and hosted on G2.com.


