MétaCan
Menu
Back to cohort

MRegTest: A Replay-Based Regression Testing Tool for Distributed UML-RT Models

2021· article· en· W4200053401 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

Venue2021 ACM/IEEE International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C) · 2021
Typearticle
Languageen
FieldComputer Science
TopicSoftware Testing and Debugging Techniques
Canadian institutionsQueen's University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceRegression testingSemantics (computer science)Model-based testingProcess (computing)Set (abstract data type)Unified Modeling LanguageTimestampRegression analysisData miningTest caseProgramming languageMachine learningReal-time computingSoftwareSoftware system

Abstract

fetched live from OpenAlex

Regression testing is indispensable, especially for real-time distributed systems to ensure that existing functionalities are not affected by changes. In this paper, we present MRegTest, a replay-based regression testing tool for distributed systems that are developed using communicating state machine models. Despite recent advances, regression testing for distributed systems remains challenging. The inherent non-determinism typically allows systems to exhibit many different executions in response to the same input. In addition, it is often not possible to control the execution environment such that this non-determinism is removed without changing the execution semantics. MRegTest addresses the above-mentioned challenges via Automatic Mutant Generation (AMG) and Regression Testing (RT) modules. AMG facilitates regression testing by generating several mutants from a UML-RT model according to a user-defined set of critical variables. RT allows the user to detect regressions of both single or multiple modified models. It then reports regressions and enables the user to replay traces visually in a web-based application. We have evaluated MRegTest against several use cases with various complexities. The experimental results show that compared to the traditional approaches that annotate traces with timestamps and variable values MRegTest detects almost all regressions while reducing the size of the trace significantly. The tool demonstration video: https://youtu.be/lPXjmKgadQI

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.000
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.764
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0010.001
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.112
GPT teacher head0.323
Teacher spread0.211 · 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