pytest-microservices-skill

Name: pytest-microservices-skill
Author: 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.

0stars

Updated 4 months ago

View on GitHub ↗

How to add

/plugin marketplace add cdragos/agentarium

The exact command may vary by repository. Check the README on GitHub.

For the skill author

Drop this on your repo README

Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.

[![Listada na Skillteca](https://www.skillteca.com.br/api/badge/pytest-microservices-skill/svg)](https://www.skillteca.com.br/skills/pytest-microservices-skill?utm_source=badge&utm_medium=readme&utm_campaign=badge)

#llm #python #ai #test

Related skills

See all in Automação →

MoneyPrinterTurbo

84.1k

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

Automaçãoby harry0703

weather-svg-creator

55.6k

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#aiby shanraisshan

telegram-bot-builder

39.2k

Expert in building Telegram bots that solve real problems - from

Automação#github#gitby sickn33

segment-automation

39.2k

Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.

Automação#github#gitby sickn33

Category alert

Get new Automação skills every Monday

One short email with only the new Automação skills. 4 minutes of reading, no spam, unsubscribe with one click.

You confirm your email on the first send. No spam. Unsubscribe with one click.

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.]

ShareX LinkedIn

Comments · No comments

No comments yet. Be the first.