Papers for

quality assurance teams

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Input metrics compared and improved for better software testing

An analysis of the relationship of input metrics

Abstract: Input metrics evaluate the progress of testing in terms of features of inputs present in a test suite. Previous works, as early as the 1950s, established a number of such metrics, but few endeavored to compare them. This paper does so by utilizing existing methods proposed for other metric classes in partition testing literature. After defining and reviewing common input metrics, we begin with a short case study revealing that typical empirical comparison strategies are fundamentally insufficient for comparing metrics. Then, we demonstrate how one rigorously improves a standard metric by defining and implementing $k$-alt-path, a new metric which reduces redundancy while improving sensitivity over $k$-path. Each of the other common input metrics are then systematically compared before discussing the implications of our findings. With these contributions, we bring forward partition testing analysis methods that justify and form a strategy for future research in refining input metrics.

Thu 10 SeptSoftware EngineeringFormal Languages and Automata Theory
The gist
Software testers use input metrics to measure how well their tests cover different input features. This paper looks at many of these metrics and finds that common ways to compare them don't work well. The authors create a better metric called k-alt-path that reduces overlap and detects differences more effectively. They then compare other input metrics systematically and suggest ways to improve future testing measures.
Open 2609.11824v1

Implementation gaps limit coding of research methods available solutions lag

IdeaAMBIG: Benchmarking Implementation-Critical Gaps in Research-Idea Specifications

Abstract: A research idea may be novel, coherent, and scientifically plausible, yet its proposed method may remain insufficiently specified for faithful implementation. We study the codification readiness of implementation-facing research-method specifications, defined by whether they provide sufficient methodological information for a competent implementer or coding agent to construct the intended method without unsupported assumptions. We construct evidence-grounded specifications and their supported resolutions from papers, codebases, issue threads, and reproduction artifacts. We introduce IdeaAMBIG, a benchmark of 660 evidence-grounded instances: 163 real-world gaps from reproducibility reports and GitHub issues, and 497 controlled synthetic gaps injected into codification-ready references. IdeaAMBIG evaluates three capabilities: codification-readiness assessment, defect localization, and clarification action generation. Defect localization receives only the specification, whereas clarification additionally receives the annotated defect. Across 13 LLMs, the best model achieves 9.6% Macro Defect Recovery Rate on real-world instances but 80.6% Macro Clarification Action Success Rate when given the defect. In an oracle study, supplying the gold resolution raises the downstream codification-ready rate from 14% to 98%. Across all evaluated models, defect localization is the main bottleneck, with stronger clarification given the defect.

Wed 9 SeptComputation and Language
The gist
Sometimes research papers describe methods that sound good but don’t give enough detail for someone to actually build the method correctly. The authors studied how often these important missing details happen and created a collection of examples showing these gaps. They tested different large language models to see if the models can spot these missing steps and help fix them. The models often struggled to find the missing parts but did better at suggesting fixes once told what’s missing. This shows that understanding what part of a method is unclear is the hardest problem.
Open 2609.10539v1

Agentic tools improve web accessibility audits for specific guidelines

Agentic Web Accessibility Auditing: Authoring and Evaluating Per-Criterion Worker Agents for WCAG

Abstract: Automated accessibility assessments differ in the evidence they collect and the requirements they address. We present a framework that combines shared browser tools with criterion-specific worker agents, implementing 39 WCAG 2.1 Level A and AA criteria and one additional WCAG 2.2 criterion. We analyze archived predictions on 250 page-criterion records derived from professional audits of scholarly platforms. Workers recover 0.86 of positive reference labels, compared with 0.36 for axe-core and 0.67 for an uncued vision-language model, with lower precision. Criterion-level results, abstentions, development-exposure sensitivities, and separately instrumented runs qualify these comparisons. Inferred negative labels and differences between evaluated configurations limit conclusions about true accuracy and causal effects. We contribute the framework, its criterion-specific implementation, and an evaluation account that distinguishes detection, evidence availability, and resource use, motivating further study of inspectable automated assessments within professional auditing.

Tue 8 SeptHuman-Computer Interaction
The gist
Checking websites to make sure they work well for everyone, including people with disabilities, can be hard because automated tools don’t always catch all problems. The authors created a system that uses specialized agents, each focusing on a different accessibility rule from recognized guidelines, to better find issues on websites. Their system was tested on real audits and found more true problems than existing tools, though sometimes with less accuracy. This approach helps auditors see what evidence each agent uses and could make automated website accessibility checking more reliable.
Open 2609.09379v1

Reasoning formats affect how people check AI model answers

Do Reasoning Representations Help Humans Evaluate LLM Outputs?

Abstract: Reasoning representations are increasingly used as explanations for large language model outputs. Yet they are typically evaluated with model-centric criteria, such as answer accuracy and faithfulness, leaving it unclear whether they help people evaluate model responses. In this work, we study reasoning representations as human-facing interfaces rather than proxies for model reasoning ability. We conduct a controlled human study of six reasoning formats across tasks of varying complexity, supported by a web-based framework that randomizes task domains, problem instances, and representation order. The study collects fine-grained judgments of structural understanding, error detection and localization, and trust calibration. Our study shows a mismatch between perceived preference and support for human evaluation. Participants prefer planning- and decomposition-based representations, but simpler chain-of-thought traces better support verification, trust, and interpretability. Preferred representations also introduce calibration risks, with more false alarms on correct traces and high trust despite low willingness to verify.

Tue 8 SeptMachine LearningHuman-Computer Interaction
The gist
People need ways to understand and trust answers from large language models (LLMs). The authors studied six different ways to show the reasoning behind LLM answers to see which best helps people check and trust those answers. They found that while many people liked clear, structured plans, the simplest step-by-step reasoning helped them spot errors and decide whether to trust the answer better. Some preferred formats made people too confident or triggered unnecessary doubts, showing a mismatch between what users like and what works best for verifying AI outputs.
Open 2609.09038v1

LLM robustness tested using noisy and altered input tasks

LANTERN: Language Model Assessment on Noisy and Transformed Tasks for Understanding Error and Robustness Nuances

Abstract: Robustness evaluation of large language models (LLMs) remains a critical challenge, particularly in assessing their sensitivity to perturbations in input data. In this work, we systematically evaluate LLM robustness across multiple dimensions, including word error rate, character repetition and duplication, modifications in choices, and variability in instruction following. To facilitate this evaluation, we construct a synthetic and augmented dataset encompassing a diverse set of LLM benchmarks, specifically targeting multiple-choice question (MCQ) datasets and instruction-following tasks. We conduct extensive experiments on LLMs of varying scales-small, medium, and large-as well as across base and instruction-tuned variants. Our analysis quantifies the variability in model responses under perturbed conditions and highlights discrepancies relative to baseline models. The findings provide insights into the stability of LLMs across different evaluation scenarios contributing to the development of more robust and reliable language models as well as robust evaluation methodologies.

Mon 7 SeptComputation and LanguageArtificial Intelligence
The gist
Knowing how well large language models (LLMs) handle mistakes or changes in text is important to trust their answers. The authors created a set of tasks that mix up words, repeat characters, and change question options to see how these models react. They tested many models of different sizes and types to find out which ones handle errors better or worse. Their work helps show areas where models need to improve so they can give more reliable answers even with messy input.
Open 2609.07309v1