MétaCan
Menu
Back to cohort
Record W48642625

Validation Against Actual Behavior: Still a Challenge for Testing Tools.

2010· article· en· W48642625 on OpenAlexaff
Dave Arnold, Jean‐Pierre Corriveau, Wei Shi

Bibliographic record

VenueSoftware Engineering Research and Practice · 2010
Typearticle
Languageen
FieldComputer Science
TopicSoftware Testing and Debugging Techniques
Canadian institutionsOntario Tech UniversityCarleton University
Fundersnot available
KeywordsComputer scienceTraceabilitySoftware engineeringAcceptance testingModel-based testingQuality (philosophy)Code (set theory)Test (biology)Test caseProgramming languageMachine learning
DOInot available

Abstract

fetched live from OpenAlex

A quality-driven approach to software development and testing demands that, ultimately, the requirements of stakeholders be validated against the actual behavior of an implementation under test (IUT). Current approaches and tools for testing fall into one of two categories: code-centric or model-centric. In this paper we review typical tools offered in each of these two categories, in order to establish the ability of such tools to support validation against actual behavior. We postulate that such support requires that test cases be both a) traceable back to the requirements of stakeholders and b) executed using an actual IUT in order to determine their outcome based on the actual behavior of an IUT. We observe that, in general, code-based testing tools fail to offer traceability between stakeholders' requirements and test cases. In contrast, in model-based testing, tests are generated from and traceable back to models, but they are typically disconnected from an actual IUT. Thus, we argue that validation against actual behavior remains a challenge for most existing code-centric and model-centric testing tools. We conclude by suggesting some essential functionality for a testing tool that could support the validation of the requirements of stakeholders against the actual behavior of an

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.056
metaresearch head score (Gemma)0.239
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.056
Threshold uncertainty score0.296

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0560.239
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0020.002
Science and technology studies0.0010.006
Scholarly communication0.0070.013
Open science0.0060.005
Research integrity0.0040.005
Insufficient payload (model declined to judge)0.0020.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.135
GPT teacher head0.378
Teacher spread0.243 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations3
Published2010
Admission routes1
Has abstractyes

Explore more

Same venueSoftware Engineering Research and PracticeSame topicSoftware Testing and Debugging TechniquesFrench-language works237,207