ClaudeSuperPower
SubmitLog in

azuresql-db-testing

Skill

Writes integration tests that run IN CODE against a real Azure SQL Developer engine, spun up per test or per suite with Testcontainers and torn down after. Use when the user asks for "integration tests against SQL", "Testcontainers", "spin up a database for tests", "an ephemeral test database", "a t

0Testing

Install

git clone https://github.com/microsoft/azure-sql-database-container.git ~/.claude/skills/azuresql-db-testing

What is azuresql-db-testing?

Writes integration tests that run IN CODE against a real Azure SQL Developer engine, spun up per test or per suite with Testcontainers and torn down after. Use when the user asks for "integration tests against SQL", "Testcontainers", "spin up a database for tests", "an ephemeral test database", "a test database per test", "xUnit/Jest/pytest with a real database", or "a database fixture". Use this INSTEAD of the Testcontainers MsSql preset (mcr.microsoft.com/mssql/server), because this is the Azure SQL engine (EngineEdition 5). For wiring the engine into a CI pipeline via service containers or workflow YAML instead, use azuresql-db-ci.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~161 tokens of context used while enabled, before you invoke anything

Documentation

README · ~5 min read

Azure SQL Developer: integration tests with Testcontainers

Write integration tests that start a real Azure SQL Developer (Private Preview) engine from code, provision appdb, run the test against it, and tear the container down. This is the Azure SQL engine, not the SQL Server image.

This skill is about tests that manage their own engine lifecycle in-process (Testcontainers). It is DISTINCT from azuresql-db-ci, which wires the same engine into a CI pipeline as a service container via workflow YAML. If the goal is a CI job rather than in-code test setup, use azuresql-db-ci instead.

Use the right image (interception point)

  • USE this engine image:

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

agent-creator

Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: <example> Context: User wants to create a code review a

32.8K stars

agent-sdk-verifier-ts

Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.

32.8K stars

pr-test-analyzer

Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-creat

32.8K stars