READ BEFORE writing or running automated database tests with PHPUnit, SQLite or MySQL. Prevents main-database pollution, SQLite/MySQL incompatibilities and hidden regressions.
Installs into .claude/skills of the current project.
Are you the author of C2f Database Testing?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/otavioserra-c2f-database-testing-conn2flow-ai-workspace)
---
name: c2f-database-testing
description: "READ BEFORE writing or running automated database tests with PHPUnit, SQLite or MySQL. Prevents main-database pollution, SQLite/MySQL incompatibilities and hidden regressions."
user-invocable: false
---
# Isolated tests of database Conn2Flow
# ⚡ MANDATORY TRIGGER
- **TRIGGER**: Write, run or debugging unit or integration automated tests that access database tables.
- **SKIP ONLY IF**: Pure unit testing (with complete mocking) or unique JavaScript (Vitest/happy-dom) tests.
- **CONSEQUENCE OF IGNORING**: Tests fail CI/CD due to SQLite/MySQL incompatibility or unduly pollute the local development base `conn2flow_test`.
---
1. Prefer SQLite in memory for pure functions, isolated CRUD and flow with transport/resolvers injection.
2. When MySQL semantics are indispensable, use only the dedicated database `conn2flow_test` in the local container.
3. Never run destructive tests against database development `conn2flow`.
4. Create the required minimum schema, isolate fixtures and remove the database/test tables at the end.
5. Use autorun guards to include controllers directly and inject PDO/configuration instead of relying on full bootstrap.
6. If a test changes manifests or versioned data files, restore only these side effects out of scope and confirm diff.
