How do I install the Docker Testing skill?

Run npx skillmds add majiayu000/docker-testing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Docker Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Docker Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Docker Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Docker Testing?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Docker Testing by majiayu000 — Agent Skill

Name: Docker Testing
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

Docker Testing Skill

Use this skill whenever you need to run the project’s test suite or diagnose issues inside Docker containers. It provides a summary of common commands and troubleshooting steps.

Running the test suite

Build and start services: Use docker compose -f docker/docker-compose.yaml up --build to build all images and start the services in development mode.
Run backend tests: Execute docker compose -f docker/docker-compose.yaml exec backend python -m pytest to run the backend test suite.
Run frontend tests: For frontend unit tests, run docker compose -f docker/docker-compose.yaml exec frontend npm run test or use the appropriate Vitest command.
Check logs: View logs for all services with docker compose -f docker/docker-compose.yaml logs -f or for a specific service with docker compose -f docker/docker-compose.yaml logs -f backend or frontend.
Stop services: Shut down all running containers with docker compose -f docker/docker-compose.yaml down. Include the -v flag to remove volumes for a clean start.

Troubleshooting tips

Port conflicts: If services fail to start, check that the default ports (backend 8000, frontend 8080) are free. Modify port mappings in the compose file if necessary.
Database issues: Ensure that the database service is healthy by running docker compose -f docker/docker-compose.yaml ps and looking for the “(healthy)” status. Check docker compose -f docker/docker-compose.yaml logs db for errors.
API connection errors: Test the backend directly with curl http://localhost:8000/docs to confirm it’s running. Verify the Nginx configuration in client/nginx.conf if the frontend cannot reach /api/* endpoints.

Best practices

Run tests in a clean environment. Stop containers and remove volumes if you suspect stale state.
Use relative paths and environment variables. Avoid hard‑coded host dependencies so your setup is portable.
When debugging, read container logs before rerunning tests. This saves time and surfaces issues like missing migrations or syntax errors.

---name: docker-testingdescription: Guidance for running and debugging tests in Docker environments for FastAPI + Vue/Tailwind projects.--- # Docker Testing Skill Use this skill whenever you need to run the project’s test suite or diagnose issues inside Docker containers. It provides a summary of common commands and troubleshooting steps. ## Running the test suite - **Build and start services:** Use `docker compose -f docker/docker-compose.yaml up --build` to build all images and start the services in development mode. - **Run backend tests:** Execute `docker compose -f docker/docker-compose.yaml exec backend python -m pytest` to run the backend test suite. - **Run frontend tests:** For frontend unit tests, run `docker compose -f docker/docker-compose.yaml exec frontend npm run test` or use the appropriate Vitest command. - **Check logs:** View logs for all services with `docker compose -f docker/docker-compose.yaml logs -f` or for a specific service with `docker compose -f docker/docker-compose.yaml logs -f backend` or `frontend`. - **Stop services:** Shut down all running containers with `docker compose -f docker/docker-compose.yaml down`. Include the `-v` flag to remove volumes for a clean start. ## Troubleshooting tips - **Port conflicts:** If services fail to start, check that the default ports (backend 8000, frontend 8080) are free. Modify port mappings in the compose file if necessary. - **Database issues:** Ensure that the database service is healthy by running `docker compose -f docker/docker-compose.yaml ps` and looking for the “(healthy)” status. Check `docker compose -f docker/docker-compose.yaml logs db` for errors. - **API connection errors:** Test the backend directly with `curl http://localhost:8000/docs` to confirm it’s running. Verify the Nginx configuration in `client/nginx.conf` if the frontend cannot reach `/api/*` endpoints. ## Best practices - Run tests in a clean environment. Stop containers and remove volumes if you suspect stale state. - Use relative paths and environment variables. Avoid hard‑coded host dependencies so your setup is portable. - When debugging, read container logs before rerunning tests. This saves time and surfaces issues like missing migrations or syntax errors.

Frequently asked questions