Evolutions
Galtea platform generates variations of test cases to enhance test coverage and robustness
Understanding Quality Test Evolutions
When Galtea generates Quality Tests from a ground_truth_file_path, it can also create variations of the base test cases to enhance test coverage and robustness. This is controlled by the variants parameter in the SDK and API.
In the SDK, the evolutions are known as variants, and the same parameter is used for both Quality Tests and Red Teaming Tests. However, the available options differ between the two types of tests.
What Are Quality Test Evolutions?
Quality test evolutions (also called “variants”) are systematic modifications of test cases that help evaluate your product’s robustness against a wide range of real-world user behaviors and edge cases. By selecting different evolution types, you can generate test case variations that probe for weaknesses and ensure your product performs reliably under diverse conditions.
Available Evolution Types
Below is the full list of evolution types you can select, along with their descriptions:
| Evolution Type | Description |
|---|---|
| Paraphrased | Rephrase the question to maintain the same meaning but use different wording. |
| Expanded Question | Expand the query by adding more details or making it broader. |
| Specific Focus Question | Focus on a specific part of the context to generate a more detailed query. |
| Ambiguous | Lack of clarity or specificity in the query. |
| Incorrect | Factual inaccuracies or misunderstandings in the query. |
| Incomplete | Missing key details in the query. |
| Typos | Misspelled words or accidental letter swaps in the query. |
| Slang | Use of colloquial or informal expressions. |
| Abbreviations | Shortened forms of words or acronyms. |
| Unconventional Phrasing | Rearranging words or using uncommon sentence structures. |
| Combined Topics | Combine multiple related topics into a single query. |
| Novel Phrasing | Use creative or novel phrasing not typically seen in training data. |
| Hypothetical Scenarios | Introduce hypothetical or edge-case scenarios related to the original query. |
| Informal | Incorporate vernacular, text speak, and abbreviations. Use informal, everyday language specific to a region or community, including slang and shorthand. |
| Linguistic Diverse | Mix languages or dialects within the same query, reflecting the user’s bilingual or dialectal background. |
| Typographic Error | Introduce grammatical errors, misspellings, or unconventional sentence structures, including phonetic spellings and mixed-up letters. Considers neurodivergent forms of writing such as those associated with dyslexia or learning disabilities. |
| Cognitively Diverse | Present thoughts in a non-linear fashion, with rapid shifts in topics or ideas, reflecting variable attention spans. |
Note: The available options in the Galtea UI may use slightly different names than the
variantsparameter in the SDK/API. For example,paraphrased,typos,incorrect,cognitively_diverse, andlinguistic_diverseare directly supported as variants. Other evolution types may be available in the UI for future expansion or custom use cases.
These evolutions help assess your product’s understanding and resilience by simulating real-world user behavior and edge cases. For more details on configuring variants, see the Test Creation API documentation.