Sign In Start Free Trial

Book Overview & Buying
Table Of Contents

Testing with f#

By : Mikael Lundin

3.7 (3)

Testing with f#

3.7 (3)

By: Mikael Lundin

Overview of this book

If you are a developer who wants to test applications using F#, this is the book for you. Basic experience of testing and intermediate experience of functional programming in F# is expected.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. The Practice of Test Automation

1. The Practice of Test Automation

Testing as a practice

Building trust

The purpose of testing

Testing with intent

Writing tests for regression

Summary

2. Writing Testable Code with Functional Programming

2. Writing Testable Code with Functional Programming

Purely functional

Immutability

Writing testable code

Expressiveness through functional programming

Summary

3. Setting Up Your Test Environment

3. Setting Up Your Test Environment

F# Interactive

Testing with Visual Studio

Comparing MSTest, NUnit, and xUnit

Tools and frameworks

Executing a test suite outside Visual Studio

FAKE

Continuous integration

Summary

4. Unit Testing

4. Unit Testing

Structuring your tests

Arrange, act, assert

FsUnit

Unquote

Testing in isolation

Finding the abstraction level

Test doubles

Dependency injection

Stubbing with Foq

Mocking

Dealing with databases

Summary

5. Integration Testing

5. Integration Testing

Good integration tests

Your first integration test

Setting up and tearing down databases

Speeding up integration testing

Testing stored procedures

Data-driven testing

Testing web services

Summary

6. Functional Testing

6. Functional Testing

Specifications

Setting up TickSpec

Web-browser-based testing

Regression testing

Summary

7. The Controversy of Test Automation

7. The Controversy of Test Automation

Bugs or defects

The cost of quality

The false security of code coverage

Test-driven development

Testing or fact-checking

Summary

8. Testing in an Agile Context

8. Testing in an Agile Context

Building a bridge or tending to a garden

The broken iron triangle

Visualizing metrics

The Kanban board

Predictability

Testing in agile

Summary

9. Test Smells

9. Test Smells

Tests that break upon refactoring

Tests that break occasionally

Tests that never break

Tests that are too complex

Tests that require excessive setup

Developers not writing tests

Summary

10. The Ten Commandments of Test Automation

10. The Ten Commandments of Test Automation

Testing behavior, not implementation

Using ubiquitous language in your test name

Asserting only one thing in your test

Don't mock the Mockingbird

Always refactor your SUT

Your test should never be more than 10 lines of code

Always test in isolation

Controlling your dependencies

Your test is a ninja

The test is not complex

Summary

Index

Index

Using ubiquitous language in your test name

Let us take a look at the following code:

// don't
[<Test>]
let ``store transaction to database`` () = 
    ()

// do
[<Test>]
let ``when customer checkout the cart, the order is persisted`` () =
    ()

Use words and expressions from the domain when expressing test names.

Getting the naming right is one of the hardest parts for the new tester. Before you know how to name your test, you need to know what to test, and before you know what to test you need to know what the feature is all about.

A good test name should state something about the feature, so obvious that a business analyst would agree with it. The test name should also reflect on what we're asserting.

In order to achieve this, I usually start my test names with the should word, and let the fixture hold the name of the feature as follows:

when submitting the form.should warn about invalid e-mail address
when submitting the form.should store the user profile to database...

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Testing with f#

Search

Your notes and bookmarks