Series kickoff: Rovo in Testing — how teams actually get value from AI when the work still lives in Jira.
The ask that usually fails:
“Write me some test cases for login.”
You get generic steps, invented data, and nothing tied to the story your team is shipping.
Asks that work better:
• Point Rovo at a real issue (or paste the acceptance criteria)
• Ask for a skeleton: preconditions, happy path, a few negatives
• Require the reply to cite only what is in that issue / paste — not invent keys
Rovo is strong at first drafts when the context is grounded. It is weak when the prompt is a blank wish.
How are you prompting today — issue key, pasted AC, or “write me tests”?
Next week: when an AI draft is useful vs when it is dangerous.
