Sometimes, when you are performing unit or integration tests whilst developing code, you need to be able to do something extreme, such as mangling a test database or two, repeatedly, each time subsequently restoring it to its original state before running the next test. Often, especially in integration tests when you are testing processes, you will need run a ‘setup’ process to establish a known database data state, then run the process, test that the final data state matches that which your business rules dictate it should be, and finally run a ‘teardown’ process to restore things to how they were at the start.
The difference with a unit test is that the developer is constantly running the test and resents it if the set up or teardown processes take any delay longer than what in my misspent youth we’d call ‘the time it takes to roll a cigarette.' Integration tests are generally done in a more dignified manner after the build, so there is less pressure on time. In this case, it is a unit test that we need, though it can be adapted as an integration test if the component under test gets to be part of a process.