Communitygithub.com

fsharp-testing

Padrões de teste em F# com xUnit, FsUnit, Unquote, FsCheck para testes baseados em propriedades, testes de integração e melhores práticas de organização de testes. Use ao escrever testes em F# com xUnit, FsUnit, Unquote ou FsCheck.

O que é fsharp-testing?

Esta skill fornece um guia completo de padrões de teste para aplicações F# utilizando o ecossistema moderno do .NET, com foco em xUnit como framework principal, FsUnit e Unquote para asserções expressivas, e FsCheck para testes baseados em propriedades. Ela cobre desde a estrutura básica de testes unitários com sintaxe amigável ao F# até técnicas avançadas como testes assíncronos com `task {}` e testes parametrizados com `[<Theory>]`. A skill também aborda mocking de dependências, preferindo stubs de funções — abordagem mais idiomática em F# — e inclui exemplos com NSubstitute para interfaces .NET. Para testes de integração, são apresentados padrões com WebApplicationFactory (ASP.NET Core) e Testcontainers. A organização recomendada de diretórios e a lista de antipadrões comuns ajudam a manter uma base de testes limpa e sustentável. A documentação é compatível com assistentes de codificação como Claude Code, Cursor e Codex, oferecendo comandos de terminal prontos para uso como `dotnet test` e filtros específicos.

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

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Padrões de Teste em F#

Padrões abrangentes de teste para aplicações F# usando xUnit, FsUnit, Unquote, FsCheck e práticas modernas de teste no .NET.

Quando Ativar

  • Escrevendo novos testes para código F#
  • Revisando qualidade e cobertura de testes
  • Configurando infraestrutura de teste para projetos F#
  • Debugando testes lentos ou instáveis

Pilha de Frameworks de Teste

FerramentaPropósito
xUnitFramework de teste (escolha padrão do ecossistema .NET)
FsUnit.xUnitSintaxe de asserção amigável ao F# para xUnit
UnquoteBiblioteca de asserção que usa citações F# para mensagens de falha claras
FsCheck.xUnitTestes baseados em propriedades integrados com xUnit
NSubstituteMock de dependências .NET
TestcontainersInfraestrutura real em testes de integração
WebApplicationFactoryTestes de integração ASP.NET Core

Testes Unitários com xUnit + FsUnit

Estrutura Básica de Teste

module OrderServiceTests

open Xunit
open FsUnit.Xunit

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

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

Asserções com Unquote

Unquote usa citações F# para que as mensagens de falha mostrem a expressão completa que falhou, não apenas "esperado X, recebido Y".

module OrderValidationTests

open Xunit
open Swensen.Unquote

[<Fact>]
let ``PlaceOrder retorna sucesso quando requisição é válida`` () =
    let request = { CustomerId = "cust-123"; Items = [ validItem ] }
    let result = OrderService.placeOrder request
    test <@ Result.isOk result @>

[<Fact>]
let ``total do pedido soma preços dos itens`` () =
    let items = [ { Sku = "A"; Quantity = 2; Price = 10m }
                  { Sku = "B"; Quantity = 1; Price = 5m } ]
    let total = Order.calculateTotal items
    test <@ total = 25m @>

[<Fact>]
let ``email validado rejeita entrada vazia`` () =
    let result = ValidatedEmail.create ""
    test <@ Result.isError result @>

Testes Assíncronos

[<Fact>]
let ``PlaceOrder retorna sucesso quando requisição é válida`` () = task {
    let deps = createTestDeps ()
    let request = { CustomerId = "cust-123"; Items = [ validItem ] }

    let! result = OrderService.placeOrder deps request

    test <@ Result.isOk result @>
}

[<Fact>]
let ``PlaceOrder retorna erro quando itens estão vazios`` () = task {
    let deps = createTestDeps ()
    let request = { CustomerId = "cust-123"; Items = [] }

    let! result = OrderService.placeOrder deps request

    test <@ Result.isError result @>
}

Testes Parametrizados com Theory

[<Theory>]
[<InlineData("")>]
[<InlineData("   ")>]
let ``PlaceOrder rejeita ID de cliente vazio`` (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 retorna resultado esperado`` (email: string, expected: bool) =
    test <@ EmailValidator.isValid email = expected @>

Testes Baseados em Propriedades com FsCheck

Usando FsCheck.xUnit

open FsCheck
open FsCheck.Xunit

[<Property>]
let ``total do pedido é sempre não negativo`` (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 ``serialização mantém identidade`` (order: Order) =
    let json = JsonSerializer.Serialize order
    let deserialized = JsonSerializer.Deserialize<Order> json
    deserialized = order

Geradores Personalizados

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 ``emails válidos passam na validação`` (email: string) =
    EmailValidator.isValid email

Mock de Dependências

Stubs de Funções (Preferido)

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 salva o pedido confirmado`` () = 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 para Interfaces .NET

open NSubstitute

[<Fact>]
let ``chama repositório com ID correto`` () = 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>())
}

Testes de Integração 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 retorna 404 quando não encontrado`` () = task {
        let! response = client.GetAsync($"/api/orders/{Guid.NewGuid()}")
        test <@ response.StatusCode = HttpStatusCode.NotFound @>
    }

Organização de Testes

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

Antipadrões Comuns

AntipadrãoCorreção
Testar detalhes de implementaçãoTestar comportamento e resultados
Estado compartilhado mutável em testesEstado novo por teste
Thread.Sleep em testes assíncronosUsar Task.Delay com timeout ou helpers de polling
Asserção sobre saída de sprintfAsserção sobre valores tipados e casamento de padrões
Ignorar CancellationTokenSempre passar e verificar cancelamento
Pular testes baseados em propriedadesUsar FsCheck para qualquer função com invariantes claros

Skills Relacionadas

  • dotnet-patterns - Padrões idiomáticos .NET, injeção de dependência e arquitetura
  • csharp-testing - Padrões de teste em C# (infraestrutura compartilhada como WebApplicationFactory e Testcontainers também se aplica ao F#)

Executando Testes

# Executar todos os testes
dotnet test

# Executar com cobertura
dotnet test --collect:"XPlat Code Coverage"

# Executar projeto específico
dotnet test tests/MyApp.Tests/

# Filtrar por nome do teste
dotnet test --filter "FullyQualifiedName~OrderService"

# Modo watch durante desenvolvimento
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.

Habilidades Relacionadas