backend-tests

Name: backend-tests
Author: devmauriciopineda

Use when writing or modifying backend tests under backend/src/test. Covers JUnit 5, Mockito, MockMvc, Testcontainers and the coverage gate.

by devmauriciopineda(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Instruction file imported from devmauriciopineda/careme (.github/instructions/backend-tests.instructions.md). Copyright stays with the author.

Backend tests — Careme

Stack: JUnit 5, Mockito, MockMvc, Spring Boot Test, AssertJ, Testcontainers.

Unit-test services with Mockito; use @WebMvcTest + MockMvc for controllers and @SpringBootTest + Testcontainers for integration paths that need PostgreSQL.
Assert with AssertJ; one behavior per test, names describe the behavior, not the method.
Integration tests need a reachable container runtime (Podman exposes a Docker-compatible API).
Run .\mvnw.cmd test for the suite and .\mvnw.cmd verify for the suite plus the JaCoCo coverage gate before considering work done.
Keep the fake LLM modes selected explicitly for tests — backend/src/test/resources/application.properties sets careme.llm.mode=fake — so the suite runs without network access even though the application's default is the real assistant.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

devmauriciopineda-careme-backend-tests-instructions.ocm.jsonjson

{
  "ocm": "1",
  "id": "devmauriciopineda-careme-backend-tests-instructions",
  "kind": "skill",
  "name": "backend-tests",
  "description": "Use when writing or modifying backend tests under backend/src/test. Covers JUnit 5, Mockito, MockMvc, Testcontainers and the coverage gate.",
  "publisher": "devmauriciopineda",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "github-instructions"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Use when writing or modifying backend tests under backend/src/test. Covers JUnit 5, Mockito, MockMvc, Testcontainers and the coverage gate."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-instructions",
      "repository": "https://github.com/devmauriciopineda/careme",
      "path": ".github/instructions/backend-tests.instructions.md",
      "ref": "f7ab4e84a5814f6af1c9232b18b1a8a1bfebd8ea",
      "url": "https://github.com/devmauriciopineda/careme/blob/f7ab4e84a5814f6af1c9232b18b1a8a1bfebd8ea/.github/instructions/backend-tests.instructions.md",
      "key": "devmauriciopineda/careme/.github/instructions/backend-tests.instructions.md"
    },
    "applies_to": "backend/src/test/**"
  },
  "instructions": "# Backend tests — Careme\n\nStack: JUnit 5, Mockito, MockMvc, Spring Boot Test, AssertJ, Testcontainers.\n\n- Unit-test services with Mockito; use `@WebMvcTest` + MockMvc for controllers and\n  `@SpringBootTest` + Testcontainers for integration paths that need PostgreSQL.\n- Assert with AssertJ; one behavior per test, names describe the behavior, not the method.\n- Integration tests need a reachable container runtime (Podman exposes a Docker-compatible API).\n- Run `.\\mvnw.cmd test` for the suite and `.\\mvnw.cmd verify` for the suite plus the JaCoCo\n  coverage gate before considering work done.\n- Keep",
  "cost": {
    "context_tokens": 210
  }
}

Fetch it by URL: GET /api/v1/registry/devmauriciopineda-careme-backend-tests-instructions/manifest?version=1.0.0

About

Backend tests — Careme

Use it

Manifest

Reviews