Open stanlemon opened 6 years ago
We also need to watch out for things like this: https://github.com/salesforce/storm-dynamic-spout/pull/60
I'm guilty of falling into the same trap with the PresistenceAdapter tests previously. There may be a few other spots where we aren't properly closing out background/async threads in tests. These start to pile up as essentially leaks (memory and CPU)
The purpose of this issue to track improvements in our test suite runtime.
I cleaned up and reviewed the output from one of our test runs. There are a handful of test classes that consume the bulk of execution time. I suspect a few factors are at play we should investigate:
I got the output below by looking for any test classes that took longer than 10 seconds to execute, and then from there I filtered out any individual test function less than 1 second.