It's not strictly necessary to be able to profile our unit tests specifically, but it's at least one convenient avenue for identifying unexpected sticking points. Alternative solutions include a different set of benchmarks that don't use "unittest" to identify this type of issue.
As we continue to engineer the code more and more, it's important to have performance tests as well, to make sure introducing a convenient abstraction didn't slow the code down by 50%.
The current unit test framework circumvents the use of standard profilers for some reason.
E.g.
vs
It's not strictly necessary to be able to profile our unit tests specifically, but it's at least one convenient avenue for identifying unexpected sticking points. Alternative solutions include a different set of benchmarks that don't use "unittest" to identify this type of issue.
As we continue to engineer the code more and more, it's important to have performance tests as well, to make sure introducing a convenient abstraction didn't slow the code down by 50%.