After using AI extensively for the last 1-2 years, I've noticed an interesting limitation.
When I ask AI to generate 10 test cases for a scenario, usually only 3-4 are highly relevant. The remaining test cases are often generic, duplicated, or based on assumptions that don't match the actual business scenario.
The problem isn't just accuracy—it's also cost(Extra Money, Water, Electricity etc).
Even the irrelevant output consumes tokens, which means:
• More tokens used
• Higher API costs
• More time spent reviewing and filtering responses
I don't think the solution is to stop using AI. Instead, we need to use it more efficiently.
A few things that have helped me:
✅ Provide complete business context and acceptance criteria.
✅ Mention constraints and assumptions explicitly.
✅ Ask for only "Top 5 high-priority test cases" instead of asking for everything.
✅ Generate test cases iteratively rather than in one big prompt.
✅ Ask AI to first identify missing information before generating the answer.
✅ Use AI as an assistant, not as a replacement for domain knowledge.
AI is incredibly powerful, but better prompting and better context are still the keys to saving both tokens and money.
Has anyone else experienced the same thing while using AI for testing or development?
Yes, I did experiment with it. Adding domain-specific context, business rules, and constraints definitely improved the relevance of the generated test cases.
AI fashion editorial. I used a selfie, a photo of the Nour Hammour "Sandy" coat, and leveraged GPT Image 2.5 Sunburst + Seedance 2.5. That Nour Hammour Paris coat is on my wishlist.
Playing around with SaaS motion using Claude + After Effects + Higgsfield.
Just started experimenting with smooth movements, little bounces, and some morphing techniques.
Still figuring things out, but this workflow is pretty interesting. If this keeps working, making a full explainer video might not take a whole week anymore. 😄