Communitygithub.com

fsharp-testing

Modèles de test F# avec xUnit, FsUnit, Unquote, FsCheck pour les tests basés sur les propriétés, tests d'intégration et bonnes pratiques d'organisation des tests.

Qu'est-ce que fsharp-testing ?

Cette compétence fournit un guide complet sur les modèles de test pour les applications F# utilisant xUnit, FsUnit, Unquote, FsCheck et les pratiques modernes de test .NET. Elle couvre la configuration de l'infrastructure de test, l'écriture de tests unitaires avec des assertions F#-friendlies, l'utilisation de tests paramétrés avec `Theory`, les tests asynchrones avec `task {}`, et les tests basés sur les propriétés avec FsCheck. La compétence inclut également des stratégies de simulation de dépendances via des stubs de fonctions et NSubstitute, des tests d'intégration ASP.NET Core avec WebApplicationFactory et Testcontainers, ainsi qu'une organisation recommandée des tests dans l'arborescence du projet. Elle met en garde contre les anti-patrons courants et fournit des commandes CLI pour exécuter les tests, avec couverture de code ou en mode surveillance. Idéale pour les développeurs F# qui souhaitent mettre en place une suite de tests robuste, maintenable et expressive.

Compatible avec~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/affaan-m/ECC/tree/main/skills/fsharp-testing

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Modèles de test F#

Modèles de test complets pour les applications F# utilisant xUnit, FsUnit, Unquote, FsCheck et les pratiques modernes de test .NET.

Quand activer

  • Écrire de nouveaux tests pour du code F#
  • Réviser la qualité et la couverture des tests
  • Mettre en place l'infrastructure de test pour des projets F#
  • Déboguer des tests instables ou lents

Pile des frameworks de test

OutilObjectif
xUnitFramework de test (choix standard de l'écosystème .NET)
FsUnit.xUnitSyntaxe d'assertion adaptée à F# pour xUnit
UnquoteBibliothèque d'assertions utilisant les quotations F# pour des messages d'échec clairs
FsCheck.xUnitTests basés sur les propriétés intégrés à xUnit
NSubstituteSimulation de dépendances .NET
TestcontainersInfrastructure réelle dans les tests d'intégration
WebApplicationFactoryTests d'intégration ASP.NET Core

Tests unitaires avec xUnit + FsUnit

Structure de test de base

module OrderServiceTests

open Xunit
open FsUnit.Xunit

[<Fact>]
let ``create définit le statut sur EnAttente`` () =
    let order = Order.create "cust-1" [ validItem ]
    order.Status |> should equal Pending

[<Fact>]
let ``confirm change le statut sur Confirmé`` () =
    let order = Order.create "cust-1" [ validItem ]
    let confirmed = Order.confirm order
    confirmed.Status |> should be (ofCase <@ Confirmed @>)

Assertions avec Unquote

Unquote utilise les quotations F# afin que les messages d'échec affichent l'expression complète qui a échoué, pas seulement "attendu X obtenu Y".

module OrderValidationTests

open Xunit
open Swensen.Unquote

[<Fact>]
let ``PlaceOrder renvoie un succès quand la requête est valide`` () =
    let request = { CustomerId = "cust-123"; Items = [ validItem ] }
    let result = OrderService.placeOrder request
    test <@ Result.isOk result @>

[<Fact>]
let ``le total de la commande additionne les prix des articles`` () =
    let items = [ { Sku = "A"; Quantity = 2; Price = 10m }
                  { Sku = "B"; Quantity = 1; Price = 5m } ]
    let total = Order.calculateTotal items
    test <@ total = 25m @>

[<Fact>]
let ``l'email validé rejette une entrée vide`` () =
    let result = ValidatedEmail.create ""
    test <@ Result.isError result @>

Tests asynchrones

[<Fact>]
let ``PlaceOrder renvoie un succès quand la requête est valide`` () = task {
    let deps = createTestDeps ()
    let request = { CustomerId = "cust-123"; Items = [ validItem ] }

    let! result = OrderService.placeOrder deps request

    test <@ Result.isOk result @>
}

[<Fact>]
let ``PlaceOrder renvoie une erreur quand les articles sont vides`` () = task {
    let deps = createTestDeps ()
    let request = { CustomerId = "cust-123"; Items = [] }

    let! result = OrderService.placeOrder deps request

    test <@ Result.isError result @>
}

Tests paramétrés avec Theory

[<Theory>]
[<InlineData("")>]
[<InlineData("   ")>]
let ``PlaceOrder rejette un ID client vide`` (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 renvoie le résultat attendu`` (email: string, expected: bool) =
    test <@ EmailValidator.isValid email = expected @>

Tests basés sur les propriétés avec FsCheck

Utilisation de FsCheck.xUnit

open FsCheck
open FsCheck.Xunit

[<Property>]
let ``le total de la commande est toujours non négatif`` (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 ``la sérialisation fait un aller-retour`` (order: Order) =
    let json = JsonSerializer.Serialize order
    let deserialized = JsonSerializer.Deserialize<Order> json
    deserialized = order

Générateurs personnalisés

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 ``les emails valides passent la validation`` (email: string) =
    EmailValidator.isValid email

Simulation de dépendances

Stubs de fonctions (recommandé)

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 sauvegarde la commande confirmée`` () = 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 pour les interfaces .NET

open NSubstitute

[<Fact>]
let ``appelle le dépôt avec le bon 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>())
}

Tests d'intégration ASP.NET Core

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 renvoie 404 quand non trouvé`` () = task {
        let! response = client.GetAsync($"/api/orders/{Guid.NewGuid()}")
        test <@ response.StatusCode = HttpStatusCode.NotFound @>
    }

Organisation des tests

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

Anti-patrons courants

Anti-patronCorrection
Tester les détails d'implémentationTester le comportement et les résultats
État de test partagé mutableÉtat frais par test
Thread.Sleep dans les tests asynchronesUtiliser Task.Delay avec timeout, ou des aides de sondage
Assertion sur la sortie de sprintfAssertion sur des valeurs typées et des filtres par motif
Ignorer CancellationTokenToujours passer et vérifier l'annulation
Ignorer les tests basés sur les propriétésUtiliser FsCheck pour toute fonction avec des invariants clairs

Compétences connexes

  • dotnet-patterns - Modèles .NET idiomatiques, injection de dépendances et architecture
  • csharp-testing - Modèles de test C# (l'infrastructure partagée comme WebApplicationFactory et Testcontainers s'applique aussi à F#)

Exécution des tests

# Exécuter tous les tests
dotnet test

# Exécuter avec couverture
dotnet test --collect:"XPlat Code Coverage"

# Exécuter un projet spécifique
dotnet test tests/MyApp.Tests/

# Filtrer par nom de test
dotnet test --filter "FullyQualifiedName~OrderService"

# Mode surveillance pendant le développement
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/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

affaan-m/ECC

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

affaan-m/fal-ai-media

Unified media generation via fal.ai MCP — image, video, and audio. Covers text-to-image (Nano Banana), text/image-to-video (Seedance, Kling, Veo 3), text-to-speech (CSM-1B), and video-to-audio (ThinkSound). Use when the user wants to generate images, videos, or audio with AI.

affaan-m/manim-video

日本語翻訳:このファイルは manim-video 用の日本語翻訳が必要です

affaan-m/remotion-video-creation

Remotion のベストプラクティス - React で動画を作成する。3D、アニメーション、音声、字幕、チャート、トランジションなどをカバーするドメイン固有の29のルール。

affaan-m/video-editing

AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.

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.

agent-self-evaluation

Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

ai-first-engineering

Engineering operating model for teams where AI agents generate a large share of implementation output. Use when setting team process, review gates, or ownership rules for a codebase largely written by agents.

ai-regression-testing

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.

android-clean-architecture

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring modules, layers, or data flow in an Android or KMP project.

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

Skills associés