Validation Against Actual Behavior: Still a Challenge for Testing Tools.
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
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.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.110 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it