Adyen augments unit test generation with LLMs, AST parsing, and Knowledge Graphs
Writing unit tests is time-consuming and manual processes introduce variability; conventional LLMs and RAG systems with vector embeddings cannot capture the interconnected, context-dependent nature of large codebases, making automated unit test generation inaccurate.
Conventional RAG systems using vector embeddings fell short for code generation because they capture only surface-level textual similarities, missing state management, dependency hierarchies, and the context-dependent meaning of code constructs.
Combining AST parsing and Knowledge Graphs with LLMs produced a tangible advancement in unit test generation, streamlining the process and bringing new depth and accuracy, and enhancing developer capabilities at Adyen.
Frequently asked questions
What did this team achieve with this AI workflow?
Combining AST parsing and Knowledge Graphs with LLMs produced a tangible advancement in unit test generation, streamlining the process and bringing new depth and accuracy, and enhancing developer capabilities at Adyen.
What tools did this team use?
LLMs, AST, Knowledge Graphs, graph database, RAG.
What results were reported?
Unit test generation quality: tangible advancement in how we approach software testing; Test generation process efficiency: streamlines the test generation process and brings a new level of depth and accuracy; LLM unit test accuracy: elevating the LLM's ability to generate unit tests accurately (source-reported, not independently verified).
What failed first in this deployment?
Conventional RAG systems using vector embeddings fell short for code generation because they capture only surface-level textual similarities, missing state management, dependency hierarchies, and the context-dependent…
How is this quality assurance AI workflow structured?
Unit test need initiated → AST parsing of codebase → Knowledge Graph construction → Graph database storage and retrieval → LLM unit test generation.