O'Reilly logo

Testing with F# by Mikael Lundin

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Speeding up integration testing

Integration tests are slow. This is not noticeable when you are at the beginning of the product life cycle and have 50 integration tests, but when you start closing on 1,000 integration tests, they will take a long time to run. This is, of course, because they are I/O-bound, waiting for network traffic.

A unit test should never take more than 10 ms to complete. This means that 1,000 unit tests will run under 10 seconds. This is enough time to make you loose focus but not enough to be called a major hurdle in your work process.

On the other hand, it is not uncommon for an integration test to take 150 ms to complete. If you have 1,000 integration tests, it will take 2–5 minutes to complete the test run. Now, this is ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required