Book Image

Testing with F#

By : Mikael Lundin
Book Image

Testing with F#

By: Mikael Lundin

Overview of this book

Related Content you might be interested in

Current Title:

Small book image
Testing with F#
Mikael Lundin
Feb, 2015 | 286 pages
No titles found
Table of Contents (17 chapters)
Testing with F#
Testing with F#
Credits
Credits
About the Author
About the Author
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
The Practice of Test Automation
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
Writing Testable Code with Functional Programming
Purely functional
Immutability
Writing testable code
Expressiveness through functional programming
Summary
3
Setting Up Your Test Environment
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
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
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
Functional Testing
Specifications
Setting up TickSpec
Web-browser-based testing
Regression testing
Summary
7
The Controversy of Test Automation
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
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
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
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

Comparing MSTest, NUnit, and xUnit

We have just taken a look at how to get started with the three different testing frameworks: MSTest, NUnit, and xUnit. How should we choose between the three?

None of these frameworks are particularly designed to work with F# or functional programming, but they apply pretty well. MSTest is a bit cumbersome, as it requires a class with the TestClass attribute in order to execute the test suite.

The following highlights the strengths of the frameworks:

  • MSTest: This is a good choice if you're not allowed to run open source in your organization.

  • NUnit: This provides great support for external test data. It is the most mature open source test framework.

  • xUnit: This is the best test framework when it comes to extensibility.

I would choose MSTest for organizations that have extremely high requirements on what kind of software you bring into a project. These could be pharmaceutical companies or those in the financial sector, in situations where compliance is more...

Previous Section
End of Section 4
Next Section