Time Series Forecasting Benchmarks Need Scenario-Grounded Stress Testing
Organizations: The Hong Kong University of Science and Technology (Guangzhou), Guangzhou, China · The University of Western Australia, Perth, Australia
Abstract
Time series forecasting (TSF) increasingly drives decisions in transportation, energy, finance, healthcare, and infrastructure, yet current evaluation remains overly narrow: standard benchmarks reward low held-out error, while robustness studies typically reduce failure to Gaussian noise, random masking, or bounded adversarial perturbations. This obscures the real failure modes of deployed forecasting systems. Input-side anomalies are not merely noisier inputs: they often reflect structured events that alter temporal dynamics, break cross-variable dependencies, induce regime shifts, or propagate from faulty sensors to downstream decisions. These semantic, causal, and system-level failures cannot be faithfully captured by i.i.d. perturbations alone. The rise of TSF foundation models makes this evaluation gap more urgent, as unauditable pretraining corpora make held-out generalization increasingly unreliable. We therefore advocate scenario-grounded stress testing. Each test instance should include historical inputs and future targets, together with a semantic scenario, an explicit failure operator, and a measurable difficulty level. This shift makes evaluation interpretable, attributable, and deployment-relevant and friendly, enabling the community to ask not only which model is accurate, but under what conditions it fails and why.
Figures & tables
| Generation | Representative Benchmarks | Treatment of Distribution Shift |
|---|---|---|
| G1 (2010s) | M3, M4 | Implicit, via domain diversity |
| G2 (2018–2022) | Monash, LTSF | Explicit, as a domain-shift experiment |
| G3 (2023–2024) | GIFT-Eval, TFB, BasicTS+ | Controlled by held-out discipline |
| G4 (2024–2025) | fev-bench, TSFM-Bench, ProbTS | Acknowledged but unmitigated |
| G5 (this work) | Scenario-grounded | Treated as the primary design variable |
| Sampled | Constructed | |
|---|---|---|
| Unstructured | Noise & Missingness (Gaussian, uniform, random masking) | Adversarial Attacks (FGSM, PGD, C&W within -balls) |
| Structured | Distribution Shift (Wild-Time, temporal drift) | Scenario-Grounded (this work) |
| ID | Ontological Property | Blind Spot in Current Evaluation |
|---|---|---|
| B1 | Temporal shape | No semantically shaped local events |
| B2 | Cross-variable structure | No cross-variable dependency disturbances |
| B3 | Mechanism coupling | No coupling of regime change and missingness |
| B4 | Causal propagation | No cascading failure propagation |
| B5 | Attributability | No exposure of scenario parameters |
| Principles P1 – P3 | Principles P4 – P6 |
| P1. Expose scenario parameters Every test instance must be released with its scenario parameters and difficulty level , so that performance can be analyzed against specific failure conditions rather than only as an aggregate. P2. Cover structural failure families A benchmark must include instances from each of F1–F4, avoiding the implicit omission of failure classes such as dependency fracture or cascading propagation. P3. Vary difficulty systematically Each family must be instantiated across an ordered range of difficulty levels, supporting robustness curves and threshold analyses rather than single-point comparisons. | P4. Separate mechanism from observation Mechanism change and observation degradation must be parameterized independently, so their individual and joint contributions to forecast error are decomposable. P5. Preserve base-sequence fidelity Failure operators must be applied to real or simulated base sequences , ensuring that the difficulty introduced remains anchored to plausible deployment conditions. P6. Report results attributably Results must be stratified by failure family, parameter, and difficulty level rather than reported as a single aggregate, so that a benchmark indicates not only how a model performs but where and why it fails. |