Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Testing with f#
  • Table Of Contents Toc
Testing with f#

Testing with f#

By : Mikael Lundin
3.7 (3)
Buy this Book
close
close
Testing with f#

Testing with f#

3.7 (3)
By: Mikael Lundin
Buy this Book

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.
Table of Contents (12 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. The Practice of Test Automation
Icon
1. The Practice of Test Automation
Icon
Testing as a practice
Icon
Building trust
Icon
The purpose of testing
Icon
Testing with intent
Icon
Writing tests for regression
Icon
Summary
2
2. Writing Testable Code with Functional Programming
Icon
2. Writing Testable Code with Functional Programming
Icon
Purely functional
Icon
Immutability
Icon
Writing testable code
Icon
Expressiveness through functional programming
Icon
Summary
3
3. Setting Up Your Test Environment
Icon
3. Setting Up Your Test Environment
Icon
F# Interactive
Icon
Testing with Visual Studio
Icon
Comparing MSTest, NUnit, and xUnit
Icon
Tools and frameworks
Icon
Executing a test suite outside Visual Studio
Icon
FAKE
Icon
Continuous integration
Icon
Summary
4
4. Unit Testing
Icon
4. Unit Testing
Icon
Structuring your tests
Icon
Arrange, act, assert
Icon
FsUnit
Icon
Unquote
Icon
Testing in isolation
Icon
Finding the abstraction level
Icon
Test doubles
Icon
Dependency injection
Icon
Stubbing with Foq
Icon
Mocking
Icon
Dealing with databases
Icon
Summary
5
5. Integration Testing
Icon
5. Integration Testing
Icon
Good integration tests
Icon
Your first integration test
Icon
Setting up and tearing down databases
Icon
Speeding up integration testing
Icon
Testing stored procedures
Icon
Data-driven testing
Icon
Testing web services
Icon
Summary
6
6. Functional Testing
chevron up
Icon
6. Functional Testing
Icon
Specifications
Icon
Setting up TickSpec
Icon
Web-browser-based testing
Icon
Regression testing
Icon
Summary
7
7. The Controversy of Test Automation
Icon
7. The Controversy of Test Automation
Icon
Bugs or defects
Icon
The cost of quality
Icon
The false security of code coverage
Icon
Test-driven development
Icon
Testing or fact-checking
Icon
Summary
8
8. Testing in an Agile Context
Icon
8. Testing in an Agile Context
Icon
Building a bridge or tending to a garden
Icon
The broken iron triangle
Icon
Visualizing metrics
Icon
The Kanban board
Icon
Predictability
Icon
Testing in agile
Icon
Summary
9
9. Test Smells
Icon
9. Test Smells
Icon
Tests that break upon refactoring
Icon
Tests that break occasionally
Icon
Tests that never break
Icon
Tests that are too complex
Icon
Tests that require excessive setup
Icon
Developers not writing tests
Icon
Summary
10
10. The Ten Commandments of Test Automation
Icon
10. The Ten Commandments of Test Automation
Icon
Testing behavior, not implementation
Icon
Using ubiquitous language in your test name
Icon
Asserting only one thing in your test
Icon
Don't mock the Mockingbird
Icon
Always refactor your SUT
Icon
Your test should never be more than 10 lines of code
Icon
Always test in isolation
Icon
Controlling your dependencies
Icon
Your test is a ninja
Icon
The test is not complex
Icon
Summary
11
Index
Icon
Index

Summary

In the end, we want to have a fully featured test suite that describes how the system works. This specification will be the best documentation available for your system, as it will get verified every time a developer commits code to the solution. It will provide a layer of protection indicating that the functionality stays the same throughout the application life cycle.

The main challenge with functional testing will always be to create a test suite that runs fast enough and provides predictable results so we can trust the process. Functional tests are the hardest to write in plenty, and they still make a fast-running and stable test suite. We need to manage this in order to stay sane and keep providing value.

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Testing with f#
End of Chapter 6
Next Chapter
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options
font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon