Affected version
3.5.6
Bug description
Observed with JUnit 5.14.3: runtime of a test file that uses ParameterizedClass grows dramatically as the number of parameterized test sets gets into the hundreds and beyond. Rewriting the test file to use ParameterizedTest reduces the runtime back to a reasonable level.
From looking at the output directory while the test suite is running, it seems like the TEST-<class>.xml is getting continuously rewritten to be slightly larger each time a test set runs. The growth in runtime combined with this observation suggests that quadratic writes are happening. Perhaps something could be adjusted to write out the report for each test set just once, and then combine them when they're all done.
Affected version
3.5.6
Bug description
Observed with JUnit 5.14.3: runtime of a test file that uses
ParameterizedClassgrows dramatically as the number of parameterized test sets gets into the hundreds and beyond. Rewriting the test file to useParameterizedTestreduces the runtime back to a reasonable level.From looking at the output directory while the test suite is running, it seems like the
TEST-<class>.xmlis getting continuously rewritten to be slightly larger each time a test set runs. The growth in runtime combined with this observation suggests that quadratic writes are happening. Perhaps something could be adjusted to write out the report for each test set just once, and then combine them when they're all done.