Any tips on safely using AI for test generation? How do you avoid potential security or quality risks?

669 viewscircle icon1 Upvotecircle icon5 Comments
Sort by:
Senior Director - Solution Architecture in Software19 days ago

AI is used for test case generation. Prompts written are thoroughly reviewed for "prompt injection" or "jailbreak" intention. After that test case review is done by humans to ensure we avoid potential risks.

Lightbulb on1
Director of Operations25 days ago

As I say, I use my I (eyes) and my I (Intelligence) before and after the AI!

The Risk Management will need:
1. Do not fully rely on AI - thoroughly review and refine AI's output. In this case, I will have to define full scenario (starting from Business Requirements to Design to the Final Product to the AI agent) - basically, my full knowledge dump to the AI agent.
2. Use multiple AI agents independently and make the best out of them as input to your thorough reviews.
3. Best is, to share 1 with the AI Agent along with your Test Plan, Test Cases and seek its views/ inputs/ refinements.

Hope this helps.

Senior Data Scientist in Miscellaneous25 days ago

As a data scientist, I'd say, trying to address (statistical) design of experiment approaches firstly (before AI based test generation) and then comparing the variety of testcases of both attempts including the probabilities of detecting failures to have at least one benchmark by the DoE cases.

Director of Engineering25 days ago

Whether its Code Generation or test generation, gates need to be built in for overview. For AI generated test , the tester should be reviewing the test and maybe even editing it for perfect use.
Also we have a mandatory code review for all code or tests so we now have 2 pairs of eyes.

CIO in Travel and Hospitality25 days ago

Follow are a some initial thoughts:

-Operationalize governance mechanisms to address assurance concerns, including quality and security.
-Ensure that all initial AI lifecycle phases (inception, elaboration, construction, etc.) involve human oversight and accountability for outcomes, regardless of the tools employed.

Lightbulb on1

Content you might like

Yes67%

No32%

Integration issues11%

Issues in communication27%

Unrealistic timelines32%

Lack of alignment between sponsor and user needs20%

Lack of quality assurance5%

Failure to define a target audience1%

Security-related release delays1%

Other (list in comments)

View Results