The JADE 2022 release meets tomorrow’s business demands.
Given a large number of tests (>10,000) and a number of developers writing those tests, it would be great to have the actual elapsed time for each test. This would enable us to highlight long running tests that could require remedial action.
We are currently running the tests in batch mode multiple times throughout the day. Presumably if such a facility were provided, the information could be included in the log file or shown on the unit test progress form if run in that mode.
Keith Domigan
It'd also be an excellent addition have this for overnight batch processing. The ability to pinpoint exactly which jobs/flows have unusual timings and get right down to the cause would be great. I think there's currently an issue whereby flows contained within flows can't be assessed though.
Having this available would also allow us to open the timings up to data visualisation or, (in future), machine learning to identify anomalies. We could even set a new baseline each release and see whether performance increases or decreases.
Could this feature be added to the JadeTestListenerIF interface?