Balancing Parameterized Test Runners for Low‑Traffic JUnit Workloads

The project must determine the optimal JUnit parameterized test strategy for a low‑traffic workload, targeting reduced execution overhead while preserving test reliability.

Constraints include potential use of JUnit 4.x with the @Parameterized runner, risk of version conflicts when introducing JUnit 5 parameterized test classes, and memory impact from large input data sets that may affect low‑resource servers.

Questions: Should the build continue using the legacy @Parameterized annotation while gradually adopting JUnit 5 parameterized test classes? Can filtering input data subsets effectively lower overhead without sacrificing coverage?