TRV-2026-2012Version 1 · Certified

Written 2026-10-20 10:43:04 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-2012
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-20T10:43:04.410468Z
status: published
lens: g_space
sector: business
headline: AI-Driven Software Testing for a Test Center of Excellence: A Systematic Mapping and Evidence Synthesis
dek: Artificial intelligence (AI) is increasingly used to automate and optimize software testing, but the evidence is distributed across heterogeneous testing activities, AI techniques, and evaluation measures. This study maps AI-driven software-testing research and translates the evidence into capabilities relevant to a Test Center of Excellence (TCoE). A systematic evidence workflow was applied to a unified audit corpus of 2,072 records, followed by focused eligibility reconciliation and full-text verification. The…
gain_title: The evidence synthesis links AI techniques to testing activities, measurable outcomes and reusable capabilities, giving test centers a governed capability model rather than a single automation tool.
problem_title: (none)
trace_subject: (none)
gain_reading: The evidence synthesis links AI techniques to testing activities, measurable outcomes and reusable capabilities, giving test centers a governed capability model rather than a single automation tool.
gain_evidence: AI should be treated in a TCoE as a governed capability layer rather than as a single automation tool | The proposed capability model links AI techniques to testing activities, measurable outcomes, reusable TCoE capabilities, and governance with human oversight.
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers screened a unified audit corpus of 2,072 records and narrowed it to a focused set of 29 records, of which 15 were primary empirical studies and 9 were secondary studies. The studies covered machine learning, reinforcement learning, search-based methods, deep learning, explainable AI and large language models applied to testing tasks.

The work matters because organizations running test centers of excellence face scattered evidence about which AI methods suit which testing tasks. The synthesis offers a structure that ties techniques to outcomes and oversight. Its practical value depends on resolving open gaps in reliability, reproducibility and standardized evaluation.
limitation: The source identifies unresolved gaps in reliability, context awareness, test-oracle support, long-term maintenance, CI/CD integration, reproducibility and standardized evaluation.
tag: Evidence-backed gain
key_points: The final focused evidence workset contained 29 records: 15 primary empirical studies and 9 secondary studies. | Excluded records included 1 scope exclusion and 4 full-text or access exclusions. | Supported testing activities included test generation, selection and prioritization, minimization, fuzzing, validation, adaptive automation and maintenance. | The capability model includes governance with human oversight.
rundown: The study applied a systematic evidence workflow to a unified audit corpus of 2,072 records, followed by eligibility reconciliation and full-text verification before arriving at the focused set.

The primary evidence spans several AI families, including evolutionary and search-based methods, deep learning, explainable AI and large language models, and maps them onto concrete testing activities.

The authors identify gaps in context awareness, test-oracle support, long-term maintenance, CI/CD integration and reproducibility that limit how far the evidence can guide adoption.
sources:
- peer_reviewed | JURNAL TEKNIK INFORMATIKA | https://doi.org/10.15408/jti.v19i2.53564 | 2026-10-20
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
fcd45af109ec2964866cd1084375caaec465d7cbfb68895da6629ea75b239c0c
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2012 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.