python-testing
Estrategias de pruebas Python usando pytest, metodología TDD, fixtures, mocking, parametrización y requisitos de cobertura.
What this skill does
# Patrones de Pruebas Python
Estrategias completas de pruebas para aplicaciones Python usando pytest, metodología TDD y buenas prácticas.
## Cuándo Activar
- Escribir código Python nuevo (seguir TDD: rojo, verde, refactorizar)
- Diseñar suites de pruebas para proyectos Python
- Revisar la cobertura de pruebas Python
- Configurar infraestructura de pruebas
## Filosofía Central de Pruebas
### Desarrollo Guiado por Pruebas (TDD)
Siempre seguir el ciclo TDD:
1. **ROJO**: Escribir una prueba que falle para el comportamiento deseado
2. **VERDE**: Escribir el código mínimo para que la prueba pase
3. **REFACTORIZAR**: Mejorar el código manteniendo las pruebas en verde
```python
# Paso 1: Escribir prueba fallida (ROJO)
def test_add_numbers():
result = add(2, 3)
assert result == 5
# Paso 2: Escribir implementación mínima (VERDE)
def add(a, b):
return a + b
# Paso 3: Refactorizar si es necesario (REFACTORIZAR)
```
### Requisitos de Cobertura
- **Objetivo**: 80%+ de cobertura de código
- **Rutas críticas**: 100% de cobertura requerida
- Usar `pytest --cov` para medir la cobertura
```bash
pytest --cov=mypackage --cov-report=term-missing --cov-report=html
```
## Fundamentos de pytest
### Estructura Básica de Pruebas
```python
import pytest
def test_addition():
"""Prueba la suma básica."""
assert 2 + 2 == 4
def test_string_uppercase():
"""Prueba la conversión a mayúsculas."""
text = "hello"
assert text.upper() == "HELLO"
def test_list_append():
"""Prueba el append de lista."""
items = [1, 2, 3]
items.append(4)
assert 4 in items
assert len(items) == 4
```
### Aserciones
```python
# Igualdad
assert result == expected
# Desigualdad
assert result != unexpected
# Veracidad
assert result # Truthy
assert not result # Falsy
assert result is True # Exactamente True
assert result is False # Exactamente False
assert result is None # Exactamente None
# Membresía
assert item in collection
assert item not in collection
# Comparaciones
assert result > 0
assert 0 <= result <= 100
# Verificación de tipo
assert isinstance(result, str)
# Prueba de excepción (enfoque preferido)
with pytest.raises(ValueError):
raise ValueError("mensaje de error")
# Verificar mensaje de excepción
with pytest.raises(ValueError, match="entrada inválida"):
raise ValueError("entrada inválida proporcionada")
```
## Fixtures
### Uso Básico de Fixtures
```python
import pytest
@pytest.fixture
def sample_data():
"""Fixture que proporciona datos de ejemplo."""
return {"name": "Alice", "age": 30}
def test_sample_data(sample_data):
"""Prueba usando el fixture."""
assert sample_data["name"] == "Alice"
assert sample_data["age"] == 30
```
### Fixture con Setup/Teardown
```python
@pytest.fixture
def database():
"""Fixture con setup y teardown."""
# Setup
db = Database(":memory:")
db.create_tables()
db.insert_test_data()
yield db # Proporcionar a la prueba
# Teardown
db.close()
def test_database_query(database):
"""Prueba operaciones de base de datos."""
result = database.query("SELECT * FROM users")
assert len(result) > 0
```
### Alcances de Fixtures
```python
# Alcance de función (por defecto) - se ejecuta por cada prueba
@pytest.fixture
def temp_file():
with open("temp.txt", "w") as f:
yield f
os.remove("temp.txt")
# Alcance de módulo - se ejecuta una vez por módulo
@pytest.fixture(scope="module")
def module_db():
db = Database(":memory:")
db.create_tables()
yield db
db.close()
# Alcance de sesión - se ejecuta una vez por sesión de pruebas
@pytest.fixture(scope="session")
def shared_resource():
resource = ExpensiveResource()
yield resource
resource.cleanup()
```
### Fixture con Parámetros
```python
@pytest.fixture(params=[1, 2, 3])
def number(request):
"""Fixture parametrizado."""
return request.param
def test_numbers(number):
"""La prueba se ejecuta 3 veces, una por cada parámetro."""
assert number > 0
```
### Fixtures Autouse
```python
@pytest.fixture(autouse=True)
def reset_config():
"""Se ejecuta automáticamente antes de cada prueba."""
Config.reset()
yield
Config.cleanup()
def test_without_fixture_call():
# reset_config se ejecuta automáticamente
assert Config.get_setting("debug") is False
```
### Conftest.py para Fixtures Compartidos
```python
# tests/conftest.py
import pytest
@pytest.fixture
def client():
"""Fixture compartido para todas las pruebas."""
app = create_app(testing=True)
with app.test_client() as client:
yield client
@pytest.fixture
def auth_headers(client):
"""Genera cabeceras de autenticación para pruebas de API."""
response = client.post("/api/login", json={
"username": "test",
"password": "test"
})
token = response.json["token"]
return {"Authorization": f"Bearer {token}"}
```
## Parametrización
### Parametrización Básica
```python
@pytest.mark.parametrize("input,expected", [
("hello", "HELLO"),
("world", "WORLD"),
("PyThOn", "PYTHON"),
])
def test_uppercase(input, expected):
"""La prueba se ejecuta 3 veces con diferentes entradas."""
assert input.upper() == expected
```
### Múltiples Parámetros
```python
@pytest.mark.parametrize("a,b,expected", [
(2, 3, 5),
(0, 0, 0),
(-1, 1, 0),
(100, 200, 300),
])
def test_add(a, b, expected):
"""Prueba la suma con múltiples entradas."""
assert add(a, b) == expected
```
### Parametrizar con IDs
```python
@pytest.mark.parametrize("input,expected", [
("[email protected]", True),
("invalid", False),
("@no-domain.com", False),
], ids=["valid-email", "missing-at", "missing-domain"])
def test_email_validation(input, expected):
"""Prueba validación de email con IDs legibles."""
assert is_valid_email(input) is expected
```
## Markers y Selección de Pruebas
### Markers Personalizados
```python
# Marcar pruebas lentas
@pytest.mark.slow
def test_slow_operation():
time.sleep(5)
# Marcar pruebas de integración
@pytest.mark.integration
def test_api_integration():
response = requests.get("https://api.example.com")
assert response.status_code == 200
# Marcar pruebas unitarias
@pytest.mark.unit
def test_unit_logic():
assert calculate(2, 3) == 5
```
### Ejecutar Pruebas Específicas
```bash
# Ejecutar solo pruebas rápidas
pytest -m "not slow"
# Ejecutar solo pruebas de integración
pytest -m integration
# Ejecutar pruebas de integración o lentas
pytest -m "integration or slow"
```
### Configurar Markers en pytest.ini
```ini
[pytest]
markers =
slow: marca pruebas como lentas
integration: marca pruebas como de integración
unit: marca pruebas como unitarias
```
## Mocking y Patching
### Mocking de Funciones
```python
from unittest.mock import patch, Mock
@patch("mypackage.external_api_call")
def test_with_mock(api_call_mock):
"""Prueba con API externa mockeada."""
api_call_mock.return_value = {"status": "success"}
result = my_function()
api_call_mock.assert_called_once()
assert result["status"] == "success"
```
### Mocking de Excepciones
```python
@patch("mypackage.api_call")
def test_api_error_handling(api_call_mock):
"""Prueba manejo de errores con excepción mockeada."""
api_call_mock.side_effect = ConnectionError("Error de red")
with pytest.raises(ConnectionError):
api_call()
api_call_mock.assert_called_once()
```
### Mocking de Context Managers
```python
@patch("builtins.open", new_callable=mock_open)
def test_file_reading(mock_file):
"""Prueba lectura de archivo con open mockeado."""
mock_file.return_value.read.return_value = "contenido del archivo"
result = read_file("test.txt")
mock_file.assert_called_once_with("test.txt", "r")
assert result == "contenido del archivo"
```
### Usar Autospec
```python
@patch("mypackage.DBConnection", autospec=True)
def test_autospec(db_mocRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.