pytest-microservices-skill

Name: pytest-microservices-skill
Author: cdragos

Automação

Autor: cdragos

Pytest test development for Python microservices. Use when writing unit tests, integration tests, fixtures, mocking external services, or setting up test infrastructure. Triggers on requests to create tests, debug failing tests, test organization, factory fixtures, parametrization, or testcontainers.

0estrelas

Atualizado há 9 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add cdragos/agentarium

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/pytest-microservices-skill/svg)](https://www.skillteca.com.br/skills/pytest-microservices-skill)

#ai #llm #python #test

Skills relacionadas

Ver todas de Automação →

MoneyPrinterTurbo

90.3k

利用AI大模型，一键生成高清短视频 Generate short videos with one click using AI LLM.

Automação por harry0703

weather-svg-creator

58.4k

Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.

Automação #ai por shanraisshan

asana-automation

41.2k

Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.

Automação #git #github por sickn33

payment-integration

41.2k

Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.

Automação #git #github por sickn33

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Pytest Development

Workflow

Identify behavior - Target a single function/behavior per test
Write the test - Plain function (never a class) with AAA structure
Run and iterate - Refine for readability and isolation

Best Practices

Write plain functions, no test classes
Name tests test_<function>_<behavior> — be specific about inputs and outcomes
One test per distinct behavior; multiple assertions are fine when verifying one operation's effects
Use parametr

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn