local-service-testing

To enforce integration testing before a pull request, this Skill identifies service dependencies from changed files and requires a local testing artifact to be posted to the issue prior to PR creation. This ensures changes are validated against actual local services.

Testing against real local services catches schema or constraint violations that mocks would miss. By mandating integration tests against live instances like databases and caches, you prevent bugs that would otherwise only be discovered later in the CI pipeline.

You can identify local service dependencies by analyzing your changed files. This Skill automatically detects which databases, caches, or queues your modifications interact with to mandate corresponding integration tests using tools like docker-compose.

Yes, you can use docker-compose to run integration tests for local service dependencies. The Skill mandates testing code changes against actual local services like databases and queues using orchestration tools to validate behavior before allowing a pull request.

The best way to prevent service-dependent bugs from reaching CI is enforcing local integration testing. This Skill requires running tests against real local services and posting a local testing artifact to the issue before PR creation to verify stability.

Yes, you must post a local testing artifact to the issue before creating a PR. This requirement ensures that code changes affecting service-dependent components have been successfully tested against real local services like databases and caches.