Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Testing with f#

You're reading from   Testing with f# Deliver high-quality, bug-free applications by testing them with efficient and expressive functional programming

Arrow left icon
Product type Paperback
Published in Feb 2015
Publisher Packt
ISBN-13 9781784391232
Length 286 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Mikael Lundin Mikael Lundin
Author Profile Icon Mikael Lundin
Mikael Lundin
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. The Practice of Test Automation FREE CHAPTER 2. Writing Testable Code with Functional Programming 3. Setting Up Your Test Environment 4. Unit Testing 5. Integration Testing 6. Functional Testing 7. The Controversy of Test Automation 8. Testing in an Agile Context 9. Test Smells 10. The Ten Commandments of Test Automation Index

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 a bit optimistic. I had an integration test suite of 850 integration tests running in 18 minutes. Why is this important?

The time it takes to run a test suite will decide whether it will be run or not. When a test suite takes a long time to...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image