Communitygithub.com

fsharp-testing

F#-Testmuster mit xUnit, FsUnit, Unquote, FsCheck Property-basierten Tests, Integrationstests und Best Practices zur Testorganisation. Verwenden Sie dies, wenn Sie F#-Tests mit xUnit, FsUnit, Unquote oder FsCheck schreiben.

Was ist fsharp-testing?

Dieses Skill beschreibt umfassende Testmuster für F#-Anwendungen unter Verwendung von xUnit, FsUnit, Unquote, FsCheck und modernen .NET-Testpraktiken. Es deckt die gesamte Testpyramide ab: von klassischen Unit-Tests mit xUnit und FsUnit über ausdrucksstarke Assertionen mit Unquote bis hin zu Property-basierten Tests mit FsCheck. Darüber hinaus werden Integrationstests mit WebApplicationFactory und Testcontainers für ASP.NET Core sowie das Mocking von Abhängigkeiten mit NSubstitute oder einfachen Funktions-Stubs behandelt. Der Skill enthält klare Richtlinien zur Testorganisation, häufige Anti-Patterns und praktische CLI-Befehle zum Ausführen und Überwachen von Tests. Er ist ideal für F#-Entwickler, die die Qualität und Zuverlässigkeit ihrer Codebasis durch strukturierte und idiomatische Tests verbessern möchten.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/affaan-m/everything-claude-code/tree/main/skills/fsharp-testing

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

F#-Testmuster

Umfassende Testmuster für F#-Anwendungen mit xUnit, FsUnit, Unquote, FsCheck und modernen .NET-Testpraktiken.

Wann aktivieren

  • Neue Tests für F#-Code schreiben
  • Testqualität und -abdeckung überprüfen
  • Testinfrastruktur für F#-Projekte einrichten
  • Fehlerhafte oder langsame Tests debuggen

Test-Framework-Stack

ToolZweck
xUnitTest-Framework (Standard im .NET-Ökosystem)
FsUnit.xUnitF#-freundliche Assertion-Syntax für xUnit
UnquoteAssertion-Bibliothek mit F#-Zitaten für klare Fehlermeldungen
FsCheck.xUnitProperty-basiertes Testen integriert in xUnit
NSubstituteMocking von .NET-Abhängigkeiten
TestcontainersEchte Infrastruktur in Integrationstests
WebApplicationFactoryASP.NET Core-Integrationstests

Unit-Tests mit xUnit + FsUnit

Grundlegende Teststruktur

module OrderServiceTests

open Xunit
open FsUnit.Xunit

[<Fact>]
let ``create setzt Status auf Pending`` () =
    let order = Order.create "cust-1" [ validItem ]
    order.Status |> should equal Pending

[<Fact>]
let ``confirm ändert Status auf Confirmed`` () =
    let order = Order.create "cust-1" [ validItem ]
    let confirmed = Order.confirm order
    confirmed.Status |> should be (ofCase <@ Confirmed @>)

Assertions mit Unquote

Unquote verwendet F#-Zitate, sodass Fehlermeldungen den vollständigen Ausdruck zeigen, der fehlgeschlagen ist, und nicht nur „Erwartet X, erhalten Y“.

module OrderValidationTests

open Xunit
open Swensen.Unquote

[<Fact>]
let ``PlaceOrder gibt Erfolg zurück, wenn Anfrage gültig ist`` () =
    let request = { CustomerId = "cust-123"; Items = [ validItem ] }
    let result = OrderService.placeOrder request
    test <@ Result.isOk result @>

[<Fact>]
let ``Bestellsumme summiert Artikelpreise`` () =
    let items = [ { Sku = "A"; Quantity = 2; Price = 10m }
                  { Sku = "B"; Quantity = 1; Price = 5m } ]
    let total = Order.calculateTotal items
    test <@ total = 25m @>

[<Fact>]
let ``validierte Email lehnt leere Eingabe ab`` () =
    let result = ValidatedEmail.create ""
    test <@ Result.isError result @>

Asynchrone Tests

[<Fact>]
let ``PlaceOrder gibt Erfolg zurück, wenn Anfrage gültig ist`` () = task {
    let deps = createTestDeps ()
    let request = { CustomerId = "cust-123"; Items = [ validItem ] }

    let! result = OrderService.placeOrder deps request

    test <@ Result.isOk result @>
}

[<Fact>]
let ``PlaceOrder gibt Fehler zurück, wenn Artikel leer sind`` () = task {
    let deps = createTestDeps ()
    let request = { CustomerId = "cust-123"; Items = [] }

    let! result = OrderService.placeOrder deps request

    test <@ Result.isError result @>
}

Parameterisierte Tests mit Theory

[<Theory>]
[<InlineData("")>]
[<InlineData("   ")>]
let ``PlaceOrder lehnt leere Kunden-ID ab`` (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("[email protected]", true)>]
[<InlineData("[email protected]", true)>]
let ``IsValidEmail gibt erwartetes Ergebnis zurück`` (email: string, expected: bool) =
    test <@ EmailValidator.isValid email = expected @>

Property-basiertes Testen mit FsCheck

Verwendung von FsCheck.xUnit

open FsCheck
open FsCheck.Xunit

[<Property>]
let ``Bestellsumme ist immer nicht-negativ`` (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 ``Serialisierung ist roundtrip-fähig`` (order: Order) =
    let json = JsonSerializer.Serialize order
    let deserialized = JsonSerializer.Deserialize<Order> json
    deserialized = order

Benutzerdefinierte Generatoren

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 ``gültige Emails bestehen die Validierung`` (email: string) =
    EmailValidator.isValid email

Mocking von Abhängigkeiten

Funktions-Stubs (bevorzugt)

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 speichert die bestätigte Bestellung`` () = 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 für .NET-Schnittstellen

open NSubstitute

[<Fact>]
let ``ruft Repository mit korrekter ID auf`` () = 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-Integrationstests

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 gibt 404 zurück, wenn nicht gefunden`` () = task {
        let! response = client.GetAsync($"/api/orders/{Guid.NewGuid()}")
        test <@ response.StatusCode = HttpStatusCode.NotFound @>
    }

Testorganisation

tests/
  MyApp.Tests/
    Unit/
      OrderServiceTests.fs
      PaymentServiceTests.fs
    Integration/
      OrderApiTests.fs
      OrderRepositoryTests.fs
    Properties/
      OrderPropertyTests.fs
    Helpers/
      TestData.fs
      TestDeps.fs

Häufige Anti-Patterns

Anti-PatternLösung
Implementierungsdetails testenVerhalten und Ergebnisse testen
Veränderlicher gemeinsam genutzter TeststatusFrischer Status pro Test
Thread.Sleep in asynchronen TestsTask.Delay mit Timeout oder Polling-Helfer verwenden
Auf sprintf-Ausgabe assertenAuf typisierte Werte und Pattern-Matches asserten
CancellationToken ignorierenImmer übergeben und Abbruch überprüfen
Property-basierte Tests überspringenFsCheck für jede Funktion mit klaren Invarianten verwenden

Verwandte Skills

  • dotnet-patterns - Idiomatische .NET-Muster, Dependency Injection und Architektur
  • csharp-testing - C#-Testmuster (gemeinsame Infrastruktur wie WebApplicationFactory und Testcontainers gilt auch für F#)

Tests ausführen

# Alle Tests ausführen
dotnet test

# Mit Codeabdeckung ausführen
dotnet test --collect:"XPlat Code Coverage"

# Bestimmtes Projekt ausführen
dotnet test tests/MyApp.Tests/

# Nach Testnamen filtern
dotnet test --filter "FullyQualifiedName~OrderService"

# Watch-Modus während der Entwicklung
dotnet watch test --project tests/MyApp.Tests/

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

accessibility

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support.

affaan-m/claude-api

Anthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.

affaan-m/everything-claude-code

End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.

affaan-m/everything-claude-code

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

affaan-m/everything-claude-code-conventions

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

affaan-m/frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.

affaan-m/gget

gget CLI and Python workflow for quick genomic database queries, sequence lookup, BLAST-style searches, enrichment checks, and reproducible bioinformatics evidence logs.

affaan-m/literature-review

Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.

affaan-m/motion-ui

Production-ready UI motion system for React/Next.js. Use when implementing animations, transitions, or motion patterns.

affaan-m/project-guidelines-example

Example project-specific skill template based on a real production application.

affaan-m/pubmed-database

Direct PubMed and NCBI E-utilities search workflows for biomedical literature, MeSH queries, PMID lookup, citation retrieval, and API-backed literature monitoring.

affaan-m/scholar-evaluation

Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.

affaan-m/uspto-database

USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.

agent-architecture-audit

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.

agent-harness-construction

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when planning or executing engineering work that agents will carry out end to end.

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

agent-payment-x402

Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

Verwandte Skills