fsharp-testing
affaan-m/ecc
F# testing patterns with xUnit, FsUnit, Unquote, and FsCheck property-based testing.
What is fsharp-testing?
Comprehensive guide to testing F# applications using xUnit, FsUnit, Unquote, FsCheck, and modern .NET testing practices. Use this when writing new tests, reviewing test quality, setting up test infrastructure, or debugging flaky tests.
- Unit testing with xUnit and FsUnit assertion syntax
- Property-based testing with FsCheck and custom generators
- Async and parameterized tests with Theory attributes
- Mocking dependencies with function stubs and NSubstitute
- ASP.NET Core integration tests with WebApplicationFactory
- Test organization patterns and anti-pattern guidance
How to install fsharp-testing
npx skills add null --skill fsharp-testingHow to use fsharp-testing
- 1.Choose a test framework: xUnit is standard; add FsUnit.xUnit for F#-friendly assertions
- 2.Write unit tests using [<Fact>] for single cases or [<Theory>] for parameterized tests
- 3.Use Unquote (test <@ expr @>) for quotation-based assertions with clear failure messages
- 4.Add property-based tests with [<Property>] and FsCheck for functions with clear invariants
- 5.Mock dependencies using function stubs (preferred) or NSubstitute for .NET interfaces
- 6.Organize tests into Unit/, Integration/, and Properties/ folders
- 7.Run tests with dotnet test and use dotnet watch test during development
Use cases
- Writing unit tests for F# business logic with clear assertion messages
- Generating test cases automatically with property-based testing to find edge cases
- Testing async workflows and Task-based code in F#
- Integration testing ASP.NET Core APIs with in-memory databases
- Mocking external dependencies like repositories and services in tests
- F# developers writing new test suites
- Teams setting up test infrastructure for F# projects
- Developers reviewing or improving test quality and coverage
- QA engineers automating F# application testing
fsharp-testing FAQ
Both work well; FsUnit uses fluent syntax (should equal X), while Unquote uses quotations (test <@ x = y @>) and shows the full expression in failure messages. Unquote is often clearer for complex assertions.
Use task { } computation expressions with [<Fact>] or [<Theory>], and use Task.Delay instead of Thread.Sleep. Always pass and verify CancellationToken parameters.
Use FsCheck for any function with clear invariants or mathematical properties (e.g., totals are non-negative, serialization roundtrips). It finds edge cases unit tests miss.
Prefer function stubs by creating test-specific dependency records with mutable state. For .NET interfaces, use NSubstitute with Substitute.For<IInterface>().
Use WebApplicationFactory<Program> with IClassFixture, configure in-memory databases, and assert on HTTP status codes and response bodies.
Full instructions (SKILL.md)
Source of truth, from affaan-m/ecc.
name: fsharp-testing description: F# testing patterns with xUnit, FsUnit, Unquote, FsCheck property-based testing, integration tests, and test organization best practices. metadata: origin: ECC
F# Testing Patterns
Comprehensive testing patterns for F# applications using xUnit, FsUnit, Unquote, FsCheck, and modern .NET testing practices.
When to Activate
- Writing new tests for F# code
- Reviewing test quality and coverage
- Setting up test infrastructure for F# projects
- Debugging flaky or slow tests
Test Framework Stack
| Tool | Purpose |
|---|---|
| xUnit | Test framework (standard .NET ecosystem choice) |
| FsUnit.xUnit | F#-friendly assertion syntax for xUnit |
| Unquote | Assertion library using F# quotations for clear failure messages |
| FsCheck.xUnit | Property-based testing integrated with xUnit |
| NSubstitute | Mocking .NET dependencies |
| Testcontainers | Real infrastructure in integration tests |
| WebApplicationFactory | ASP.NET Core integration tests |
Unit Tests with xUnit + FsUnit
Basic Test Structure
module OrderServiceTests
open Xunit
open FsUnit.Xunit
[<Fact>]
let ``create sets status to Pending`` () =
let order = Order.create "cust-1" [ validItem ]
order.Status |> should equal Pending
[<Fact>]
let ``confirm changes status to Confirmed`` () =
let order = Order.create "cust-1" [ validItem ]
let confirmed = Order.confirm order
confirmed.Status |> should be (ofCase <@ Confirmed @>)
Assertions with Unquote
Unquote uses F# quotations so failure messages show the full expression that failed, not just "expected X got Y".
module OrderValidationTests
open Xunit
open Swensen.Unquote
[<Fact>]
let ``PlaceOrder returns success when request is valid`` () =
let request = { CustomerId = "cust-123"; Items = [ validItem ] }
let result = OrderService.placeOrder request
test <@ Result.isOk result @>
[<Fact>]
let ``order total sums item prices`` () =
let items = [ { Sku = "A"; Quantity = 2; Price = 10m }
{ Sku = "B"; Quantity = 1; Price = 5m } ]
let total = Order.calculateTotal items
test <@ total = 25m @>
[<Fact>]
let ``validated email rejects empty input`` () =
let result = ValidatedEmail.create ""
test <@ Result.isError result @>
Async Tests
[<Fact>]
let ``PlaceOrder returns success when request is valid`` () = task {
let deps = createTestDeps ()
let request = { CustomerId = "cust-123"; Items = [ validItem ] }
let! result = OrderService.placeOrder deps request
test <@ Result.isOk result @>
}
[<Fact>]
let ``PlaceOrder returns error when items are empty`` () = task {
let deps = createTestDeps ()
let request = { CustomerId = "cust-123"; Items = [] }
let! result = OrderService.placeOrder deps request
test <@ Result.isError result @>
}
Parameterized Tests with Theory
[<Theory>]
[<InlineData("")>]
[<InlineData(" ")>]
let ``PlaceOrder rejects empty customer ID`` (customerId: string) =
let request = { CustomerId = customerId; Items = [ validItem ] }
let result = OrderService.placeOrder request
result |> should be (ofCase <@ Error @>)
[<Theory>]
[<InlineData("", false)>]
[<InlineData("a", false)>]
[<InlineData("user@example.com", true)>]
[<InlineData("user+tag@example.co.uk", true)>]
let ``IsValidEmail returns expected result`` (email: string, expected: bool) =
test <@ EmailValidator.isValid email = expected @>
Property-Based Testing with FsCheck
Using FsCheck.xUnit
open FsCheck
open FsCheck.Xunit
[<Property>]
let ``order total is always non-negative`` (items: NonEmptyList<PositiveInt * decimal>) =
let orderItems =
items.Get
|> List.map (fun (qty, price) ->
{ Sku = "SKU"; Quantity = qty.Get; Price = abs price })
let total = Order.calculateTotal orderItems
total >= 0m
[<Property>]
let ``serialization roundtrips`` (order: Order) =
let json = JsonSerializer.Serialize order
let deserialized = JsonSerializer.Deserialize<Order> json
deserialized = order
Custom Generators
type OrderGenerators =
static member ValidEmail () =
gen {
let! user = Gen.elements [ "alice"; "bob"; "carol" ]
let! domain = Gen.elements [ "example.com"; "test.org" ]
return $"{user}@{domain}"
}
|> Arb.fromGen
[<Property(Arbitrary = [| typeof<OrderGenerators> |])>]
let ``valid emails pass validation`` (email: string) =
EmailValidator.isValid email
Mocking Dependencies
Function Stubs (Preferred)
let createTestDeps () =
let mutable savedOrders = []
{ FindOrder = fun id -> task { return Map.tryFind id testData }
SaveOrder = fun order -> task { savedOrders <- order :: savedOrders }
SendNotification = fun _ -> Task.CompletedTask }
[<Fact>]
let ``PlaceOrder saves the confirmed order`` () = task {
let mutable saved = []
let deps =
{ createTestDeps () with
SaveOrder = fun order -> task { saved <- order :: saved } }
let! _ = OrderService.placeOrder deps validRequest
test <@ saved.Length = 1 @>
}
NSubstitute for .NET Interfaces
open NSubstitute
[<Fact>]
let ``calls repository with correct ID`` () = task {
let repo = Substitute.For<IOrderRepository>()
repo.FindByIdAsync(Arg.Any<Guid>(), Arg.Any<CancellationToken>())
.Returns(Task.FromResult(Some testOrder))
let service = OrderService(repo)
let! _ = service.GetOrder(testOrder.Id, CancellationToken.None)
do! repo.Received(1).FindByIdAsync(testOrder.Id, Arg.Any<CancellationToken>())
}
ASP.NET Core Integration Tests
type OrderApiTests (factory: WebApplicationFactory<Program>) =
interface IClassFixture<WebApplicationFactory<Program>>
let client =
factory.WithWebHostBuilder(fun builder ->
builder.ConfigureServices(fun services ->
services.RemoveAll<DbContextOptions<AppDbContext>>() |> ignore
services.AddDbContext<AppDbContext>(fun options ->
options.UseInMemoryDatabase("TestDb") |> ignore) |> ignore))
.CreateClient()
[<Fact>]
member _.``GET order returns 404 when not found`` () = task {
let! response = client.GetAsync($"/api/orders/{Guid.NewGuid()}")
test <@ response.StatusCode = HttpStatusCode.NotFound @>
}
Test Organization
tests/
MyApp.Tests/
Unit/
OrderServiceTests.fs
PaymentServiceTests.fs
Integration/
OrderApiTests.fs
OrderRepositoryTests.fs
Properties/
OrderPropertyTests.fs
Helpers/
TestData.fs
TestDeps.fs
Common Anti-Patterns
| Anti-Pattern | Fix |
|---|---|
| Testing implementation details | Test behavior and outcomes |
| Mutable shared test state | Fresh state per test |
Thread.Sleep in async tests | Use Task.Delay with timeout, or polling helpers |
Asserting on sprintf output | Assert on typed values and pattern matches |
Ignoring CancellationToken | Always pass and verify cancellation |
| Skipping property-based tests | Use FsCheck for any function with clear invariants |
Related Skills
dotnet-patterns- Idiomatic .NET patterns, dependency injection, and architecturecsharp-testing- C# testing patterns (shared infrastructure like WebApplicationFactory and Testcontainers applies to F# too)
Running Tests
# Run all tests
dotnet test
# Run with coverage
dotnet test --collect:"XPlat Code Coverage"
# Run specific project
dotnet test tests/MyApp.Tests/
# Filter by test name
dotnet test --filter "FullyQualifiedName~OrderService"
# Watch mode during development
dotnet watch test --project tests/MyApp.Tests/
Related skills
More from affaan-m/ecc and the wider catalog.
gan-style-harness
Multi-agent harness that separates generation from evaluation to autonomously build high-quality applications.
gateguard
Fact-forcing gate that blocks edits/writes/bash until concrete investigation is presented, improving output quality by +2.25 points.
generating-python-installer
Agent skill from affaan-m/ecc.
gget
Quick genomic database queries, BLAST searches, and sequence lookups via unified CLI and Python interface.
git-workflow
Git workflow patterns, branching strategies, and collaborative development best practices.
github-ops
Automate GitHub issue triage, PR management, CI/CD debugging, and releases using gh CLI.