June 2026 Summaries
2 posts from Galtea
Filter
Month:
Year:
Post Summaries
Back to Blog
Traditional software testing methodologies and mental models are not effective for evaluating language models (LLMs) due to the inherent differences in how these models function compared to typical software systems. Unlike deterministic software, LLMs produce probabilistic outputs that vary even with the same input, challenging the assumption that identical inputs yield identical outputs. Quality in LLMs is multidimensional and cannot be captured by binary pass/fail tests, as responses may be partially correct but flawed in subtle ways that degrade the user experience. Additionally, LLMs can change behavior without code modifications due to updates in model weights by providers, and their performance can vary with input distribution shifts, thereby necessitating continuous monitoring rather than static test coverage. Furthermore, defining quality for LLMs often requires domain expertise beyond the engineering team, making rubric-based scoring and domain-specific evaluation criteria essential. As such, LLM evaluation involves a distinct process that includes methods like rubric-based scoring, reference comparison, and ongoing production monitoring to ensure the model's outputs meet application needs across diverse real-world inputs.
Jun 08, 2026
1,287 words in the original blog post.
Galtea's AI agent test case generation service enhances the testing of AI products by creating synthetic test cases that align with structured inputs from a JSON Schema, allowing for more accurate and comprehensive evaluations. The generator addresses a key issue in AI testing, where agents typically interpret structured payloads rather than simple chat messages, by populating each test case with values that align with both the narrative of the case and the specifications being tested. This ensures both structural and narrative validity, making the tests more rigorous and realistic. The new approach allows for the creation of test cases across various scenarios—direct hits, edge cases, and tangential situations—each producing a JSON object that fits the schema requirements and tests the defined specifications effectively. By integrating this into their pipeline, users can benefit from a spec-aware mode that ensures the generated test cases genuinely stress-test the specifications under review, thus enhancing the robustness of AI system evaluations.
Jun 01, 2026
1,354 words in the original blog post.