MétaCan
Menu
Back to cohort
Record W2404183746

Towards a Unified Metrics Suite for JUnit Test Cases.

2014· article· en· W2404183746 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSoftware Engineering and Knowledge Engineering · 2014
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsUniversité LavalUniversité du Québec à Trois-Rivières
Fundersnot available
KeywordsUnit testingTest suiteComputer scienceJavaTest caseVariance (accounting)Test (biology)Source codeSoftwareData miningProgramming languageMachine learningRegression analysis
DOInot available

Abstract

fetched live from OpenAlex

This paper aims at proposing a unified metrics suite that can be used to quantify different perspectives related to the code of JUnit test cases. We extended existing JUnit test case metrics by introducing two new metrics. We analyzed the code of JUnit test cases of two open source Java software systems (ANT and JFREECHART). We used in total five metrics. We used the Principal Component Analysis (PCA) method in order: (1) to better understand the underlying orthogonal dimensions captured by the suite of unit test case metrics, and (2) to find whether the metrics are independent or are measuring similar structural aspects of the JUnit test code. Overall, results show that: (1) the new introduced unit test case metrics are relevant, (2) the studied unit test case metrics are not independent, and (3) the best subset (a couple) of unit test case metrics that maximizes the variance varies from one system to the other. The new introduced metrics are, however, each in the best subset of unit test case metrics that provide the best independent information that maximizes the variance for each system.

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 imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.023
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.700
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.023
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.019
GPT teacher head0.251
Teacher spread0.232 · 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