3 ms·
if you don't mind spending the effort, have a quick profile to see where the tests are taking a long time - is it initializing the real components that could be
by chii 5y ago
if you don't mind spending the effort, have a quick profile to see where the tests are taking a long time - is it initializing the real components that could be mocked?
Or are the tests themselves taking a long time because of other factors, such as IO etc?
For IO, may be there should be an abstraction over these IO api and you use an inmemory option instead for testing.
- bluGill 5y agoOf io is the problem I general solve that by testing smaller data sets. I have not found io to the local disk is slow. Of course if it is network io that is bad, but local disks are fine for the size of data in my tests