Notifications
Clear all
Topic starter
06/09/2026 3:44 pm
TL;DR: LLMs can speed up test creation, and the article argues that output quality depends less on “asking nicely” than on engineering constraints around role, stack, architecture, scope, assertions, and missing information, according to Arxan Technologies. The practical lesson is that AI-assisted QA only stays maintainable when teams treat prompts like controlled specifications, not casual instructions.
NHIMG editorial — based on content published by Arxan Technologies: Accelerating Test Creation using LLMs
By the numbers:
- AI-assisted development can significantly accelerate engineering output, with some large-scale deployments reporting over 30% improvement in development cycle efficiency.
- Gartner predicts that by 2030, about 75% of IT work will be performed by humans working alongside AI.
Questions worth separating out
Q: How should QA teams use LLMs to generate test code safely?
A: Use LLMs as constrained assistants, not autonomous authors.
Q: Why do AI-generated tests become brittle when prompts are too broad?
A: Broad prompts give the model too much freedom to invent structure, setup, and dependencies.
Q: What should teams do when an LLM leaves out key test details?
A: Require the model to flag missing information instead of filling gaps silently.
Practitioner guidance
- Define prompt boundaries before generation begins Specify role, language, framework, architecture pattern, output scope, and environment assumptions in every prompt so the model cannot improvise outside your test standard.
- Require assertions in every generated test Make validation mandatory and reject any output that only performs actions without checking expected results, because action-only scripts are not tests.
- Limit generation to the smallest reusable unit Ask for one TestNG method, one function, or one scenario at a time so the output stays readable and fits your existing automation framework.
What's in the full article
Arxan Technologies' full article covers the practical prompting structure this post intentionally leaves at a higher level:
- A worked sample prompt for Java, Selenium, and TestNG that you can adapt to your own QA pipeline
- The exact requirement sequencing used to reduce hallucinated assumptions and duplicate code
- Practical examples of output restrictions, assertion requirements, and environment assumptions
- The author’s suggested starting template for converting business scenarios into executable tests
👉 Read Arxan Technologies' guide to accelerating test creation with LLMs →
Prompt engineering for test creation: what QA teams need to know?
Explore further
06/09/2026 3:45 pm
Prompt engineering for test generation is a governance discipline, not a creativity exercise. The article’s strongest insight is that LLM output quality improves when teams define role, stack, architecture, scope, and validation requirements up front. That mirrors identity governance: systems that can act on behalf of a team need explicit boundaries before they are trusted with production work. For practitioners, the lesson is to manage prompts as controlled artefacts.
A question worth separating out:
Q: How do you know if AI-assisted test creation is actually helping?
A: Look for shorter creation cycles without a rise in flaky tests, duplicated logic, or unreviewable assertions. If output volume increases but maintenance effort rises faster, the process is creating automation debt rather than productivity. A good programme shows consistent code structure, clear validation, and easy framework integration.
👉 Read our full editorial: LLMs can accelerate test creation, but prompts need hard constraints
