What is backend-integration-testing?

A guide for testing the backend of OpenELIS Global 2, a laboratory information system. It covers integration tests, which check that several real parts of an application work together.

Writing or updating backend integration tests, testing service layers, refactoring backend code, and running one test with Maven.

It gives developers a consistent way to test service and database behavior without relying on weak checks or overly mocked components.

How DIGI-UW/OpenELIS-Global-2 configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to DIGI-UW/OpenELIS-Global-2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/DIGI-UW/OpenELIS-Global-2/develop/.ai/skills/backend-integration-testing/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/digi-uw/openelis-global-2/backend-integration-testing.svg)](https://agentmods.dev/skills/digi-uw/openelis-global-2/backend-integration-testing)

Your own site

<a href="https://agentmods.dev/skills/digi-uw/openelis-global-2/backend-integration-testing"><img src="https://agentmods.dev/badge/skills/digi-uw/openelis-global-2/backend-integration-testing.svg" alt="Measured on agentmods" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 431 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00056	$0.00431
Opus 5	$0.00028	$0.00216
Sonnet 5	$0.00011	$0.00086
Haiku 4.5	$0.00006	$0.00043

Measured 8d ago against content hash ab8891184edc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

backend-integration-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.ai/skills/backend-integration-testing/SKILL.md · 48 lines

What it actually says

Skill: Backend Integration Testing

Context

This skill provides authoritative guidance on writing and running backend integration tests in OpenELIS Global 2. It enforces the use of Testcontainers, DBUnit, and the 5-layer architecture standards.

Trigger

When a user asks to "write a test" for a backend service.
When a user asks "how to run integration tests."
When refactoring backend logic that requires regression testing.

Behavior

Always inherit from BaseWebContextSensitiveTest.
Always seed data using executeDataSetWithStateManagement in the @Before block.
Always use real services/DAOs where possible; mock only external systems (Odoo, FHIR, Mail).
Follow the verified example: Use examples/menu-service/GeneratedMenuServiceIntegrationTest.java as the blueprint.
Verify with test target: Run mvn test -Dtest=<NewTest> to verify the newly added or modified test specifically.
Harden assertions: Avoid weak assertions like assertNotNull or assertNull. Assert aggressively on exact values, specific sizes, and field states to guarantee correct business logic outcomes.

Reference

Overview - Detailed infrastructure and patterns.
Template - Boilerplate for new tests.
Example request with its complete generated Java test, grounded in the OpenELIS MenuService and its existing DBUnit fixture.

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 48 lines · 56 tokens per session scan A ab8891184edc

Subscribe to this mod's changes

backend-integration-testing is a skill published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (251 stars, last pushed today), licensed MPL-2.0. It adds 56 tokens to every session and 431 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Backend and APIs Testing carbon-design-system clinical-laboratory digital-public-goods fhir global-health health-informatics

api-testing

Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.

cyanheads/who-gho-mcp-server · 46 tokens

server-side-calls

Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.

trpc/trpc · 61 tokens

mem0-test-integration

Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…

mem0ai/mem0 · 207 tokens

prowler-test-api

Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).

prowler-cloud/prowler · 62 tokens

python-sdk

Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.

ComposioHQ/composio · 60 tokens

convex-test

Generate convex-test tests for the app's Convex functions.

openclaw/clawhub · 16 tokens

OpenELIS-Global-2: Skill for Claude Code