Agent skill

Unit Test Service Layer

by giuseppe-trisciuoglio in giuseppe-trisciuoglio/developer-kit

Provides patterns for unit testing service layer with Mockito.

MITAuto-check: notesTesting & QA

Install Unit Test Service Layer

skills CLI

$ npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install giuseppe-trisciuoglio/developer-kit unit-test-service-layer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/developer-kit-java/skills/unit-test-service-layer .claude/skills/unit-test-service-layer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "unit-test-service-layer" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-java/skills/unit-test-service-layer into .claude/skills/unit-test-service-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-test-service-layer", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-java/skills/unit-test-service-layer

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layer -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install giuseppe-trisciuoglio/developer-kit unit-test-service-layer --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/developer-kit-java/skills/unit-test-service-layer .agents/skills/unit-test-service-layer && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "unit-test-service-layer" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-java/skills/unit-test-service-layer into .agents/skills/unit-test-service-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-test-service-layer", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layer -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install giuseppe-trisciuoglio/developer-kit unit-test-service-layer --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/developer-kit-java/skills/unit-test-service-layer .cursor/skills/unit-test-service-layer && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "unit-test-service-layer" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-java/skills/unit-test-service-layer into .cursor/skills/unit-test-service-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-test-service-layer", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/giuseppe-trisciuoglio/developer-kit.git --path plugins/developer-kit-java/skills/unit-test-service-layer

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layer -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install giuseppe-trisciuoglio/developer-kit unit-test-service-layer --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/developer-kit-java/skills/unit-test-service-layer .gemini/skills/unit-test-service-layer && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "unit-test-service-layer" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-java/skills/unit-test-service-layer into .gemini/skills/unit-test-service-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-test-service-layer", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install giuseppe-trisciuoglio/developer-kit unit-test-service-layer

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layer -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/developer-kit-java/skills/unit-test-service-layer .github/skills/unit-test-service-layer && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "unit-test-service-layer" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-java/skills/unit-test-service-layer into .github/skills/unit-test-service-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-test-service-layer", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layer -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install giuseppe-trisciuoglio/developer-kit unit-test-service-layer --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/developer-kit-java/skills/unit-test-service-layer .opencode/skills/unit-test-service-layer && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "unit-test-service-layer" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-java/skills/unit-test-service-layer into .opencode/skills/unit-test-service-layer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-test-service-layer", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: unit-test-service-layer
GitHub stars: 357
Token cost: ~1.2k tokens
SKILL.md length: 377 words
Files: 2 (incl. references)
Skills in repo: 115
Repo updated: Sep 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Provides patterns for unit testing service layer with Mockito.

Works in 5 steps: Setup Test Class → Declare Mocks with @Mock and @InjectMocks → Arrange-Act-Assert with Validation → …
Testing service behaviors and business logic without database
SKILL.md covers Overview, When to Use, Instructions and Examples, plus 3 more sections
Calls mvn and gradle

What it does

Unit Test Service Layer is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides patterns for unit testing service layer with Mockito. Creates isolated tests that mock repository calls, verify method invocations, test exception scenarios, and stub external API responses. Use when testing service behaviors and business logic without database or external services.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/examples.md`).

It sits in Testing & QA, covering Unit testing. The repository describes itself as: Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI. The licence is MIT.

When your agent uses it

Testing service behaviors and business logic without database
External services

Example prompts

“Use the unit-test-service-layer skill to provide patterns for unit testing service layer with Mockito”
“/unit-test-service-layer”

Requirements

Pre-approved tools (allowed-tools): Read, Write, Bash, Glob, Grep

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Setup Test Class
Declare Mocks with @Mock and @InjectMocks
Arrange-Act-Assert with Validation
Test Exception Scenarios
Verify Complete Coverage

What it can do on your machine

Read from SKILL.md and the folder at commit fe73fb3. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Bash
- Glob
- Grep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- mvn
- gradle
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- javadoc.io
- junit.org
- assertj.github.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Unit Test Service Layer loads about 1.2k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 377 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~79
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Write, Bash, Glob, Grep
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from giuseppe-trisciuoglio/developer-kit at commit fe73fb3, republished under its MIT licence (© giuseppe-trisciuoglio). 377 words, ~1,188 tokens.

Download SKILL.mdSave it as .claude/skills/unit-test-service-layer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: unit-test-service-layer
description: Provides patterns for unit testing service layer with Mockito. Creates isolated tests that mock repository calls, verify method invocations, test exception scenarios, and stub external API responses. Use when testing service behaviors and business logic without database or external services.
allowed-tools: Read, Write, Bash, Glob, Grep

Unit Testing Service Layer with Mockito

Overview

Provides patterns for unit testing @Service classes using Mockito. Mocks repository calls, verifies method invocations, tests exception scenarios, and stubs external API responses. Enables fast, isolated tests without Spring container or database.

When to Use

Testing business logic in @Service classes
Mocking repository and external client dependencies
Verifying service interactions with mocked collaborators
Testing error handling and edge cases in services
Writing fast, isolated unit tests (no database, no API calls)

Instructions

Follow this workflow to test service layer with Mockito, including validation checkpoints:

1. Setup Test Class

Use @ExtendWith(MockitoExtension.class) to enable Mockito annotations.

2. Declare Mocks with `@Mock` and `@InjectMocks`

Use @Mock for dependencies (repositories, clients) and @InjectMocks for the service under test.

3. Arrange-Act-Assert with Validation

Arrange: Create test data and configure mock return values using when().thenReturn().

Act: Execute the service method being tested.

Assert:

Verify returned values with AssertJ assertions
Verify mock interactions with verify()
Validation checkpoint: Run test and confirm green bar

4. Test Exception Scenarios

Configure mocks to throw exceptions with when().thenThrow().

Validation checkpoint: Verify exception type and message

5. Verify Complete Coverage

Run full test suite: mvn test or gradle test
Check coverage report: mvn test jacoco:report
Validation checkpoint: Confirm all service methods have corresponding tests

Examples

Basic Service Test Pattern

java

@ExtendWith(MockitoExtension.class)
class UserServiceTest {

  @Mock
  private UserRepository userRepository;

  @InjectMocks
  private UserService userService;

  @Test
  void shouldReturnUserWhenFound() {
    // Arrange
    User expected = new User(1L, "Alice");
    when(userRepository.findById(1L)).thenReturn(Optional.of(expected));

    // Act
    User result = userService.getUser(1L);

    // Assert
    assertThat(result.getName()).isEqualTo("Alice");
    verify(userRepository).findById(1L);
  }

  @Test
  void shouldThrowWhenUserNotFound() {
    // Arrange
    when(userRepository.findById(999L)).thenReturn(Optional.empty());

    // Act & Assert
    assertThatThrownBy(() -> userService.getUser(999L))
      .isInstanceOf(UserNotFoundException.class);
  }
}

Verify Method Invocations

java

@Test
void shouldSendEmailOnUserCreation() {
  User newUser = new User(1L, "Alice", "alice@example.com");
  when(userRepository.save(any(User.class))).thenReturn(newUser);

  enrichmentService.registerNewUser("Alice", "alice@example.com");

  verify(userRepository).save(any(User.class));
  verify(emailService).sendWelcomeEmail("alice@example.com");
}

For additional patterns (multiple dependencies, argument captors, async services, InOrder verification), see references/examples.md.

Show full SKILL.md (147 more words)Show less

Best Practices

Use @ExtendWith(MockitoExtension.class) for JUnit 5 integration
Mock only direct dependencies of the service under test
Verify interactions to ensure correct collaboration
Test one behavior per test method - keep tests focused
Use descriptive variable names: expectedUser, actualUser, captor
Create real instances for value objects and DTOs (don't mock them)

Constraints and Warnings

Do not mock value objects or DTOs; create real instances with test data.
Avoid mocking too many dependencies; consider refactoring if a service has too many collaborators.
Tests must be independent; do not rely on execution order.
Be cautious with @Spy; partial mocking is harder to understand and maintain.
Do not test private methods directly; test them through public method behavior.
Argument matchers (any(), eq()) cannot be mixed with actual values in the same stub.
Avoid over-verifying; verify only interactions important to the test scenario.

References

Files

SKILL.md and 1 other file (references) in plugins/developer-kit-java/skills/unit-test-service-layer of giuseppe-trisciuoglio/developer-kit.

SKILL.md
references/examples.md

Open the folder on GitHubat commit fe73fb3

Compare with similar skills

Unit Test Service Layer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Unit Test Service Layer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Unit Test Service Layer this skillgiuseppe-trisciuoglio/developer-kit	357	—	~1.2k	Automated safety check: Notes	MIT	1 mo ago
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph	112	11 repos	~2.4k	Automated safety check: Pass	None	8 mo ago
Testing OpenLogi UIAprilNEA/OpenLogi	23k	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Go Testingcxuu/golang-skills	173	1 repos	~1.3k	Automated safety check: Pass	Apache-2.0	3 mo ago
Contractssamchon/nestia	2.2k	—	~1.3k	Automated safety check: Pass	MIT	4 days ago
Cohesion Over TestabilityEpicenterHQ/epicenter	4.8k	—	~2k	Automated safety check: Pass	Custom licence	3 days ago

Similar skills

TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
112 GitHub starsUsed in 11 repos~2.4k tokens
Testing & QAAuto-check passed
Testing OpenLogi UI
AprilNEA/OpenLogi
Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.
23k GitHub stars~1.1k tokensUpdated today
Testing & QAAuto-check passed
Go Testing
cxuu/golang-skills
A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.
173 GitHub starsUsed in 1 repo~1.3k tokens
Testing & QAAuto-check passed
Contracts
samchon/nestia
Defines self-acknowledgments for production declarations and tests.
2.2k GitHub stars~1.3k tokensUpdated 4 days ago
Testing & QAAuto-check passed
Cohesion Over Testability
EpicenterHQ/epicenter
Collapse test-shaped production boundaries while preserving behavior and coverage.
4.8k GitHub stars~2k tokensUpdated 3 days ago
Testing & QAAuto-check passed
JS-in-HTML Testing
liaohch3/claude-tap
Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.
3.3k GitHub stars~924 tokensUpdated yesterday
Testing & QAAuto-check passed

More from giuseppe-trisciuoglio/developer-kit

All 115 skills in this repo

Nestjs Drizzle Crud Generator
giuseppe-trisciuoglio/developer-kit
Generates complete CRUD modules for NestJS applications with Drizzle ORM.
357 GitHub stars~1.3k tokensUpdated 1 mo ago
Auto-check: notes
Spring Boot Actuator
giuseppe-trisciuoglio/developer-kit
Provides patterns to configure Spring Boot Actuator for production-grade monitoring, health probes, secured management endpoints, and Micrometer metrics across JVM services.
357 GitHub stars~2.2k tokensUpdated 1 mo ago
Auto-check: notes
Spring Boot Crud Patterns
giuseppe-trisciuoglio/developer-kit
Provides and generates complete CRUD workflows for Spring Boot 3 services.
357 GitHub stars~2.5k tokensUpdated 1 mo ago
Auto-check: notes
Spring Boot Security JWT
giuseppe-trisciuoglio/developer-kit
Provides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based…
357 GitHub stars~3.9k tokensUpdated 1 mo ago
Auto-check: notes
AWS CLI Beast
giuseppe-trisciuoglio/developer-kit
Provides advanced AWS CLI patterns for managing EC2, Lambda, S3, DynamoDB, RDS, VPC, IAM, and CloudWatch.
357 GitHub stars~1.7k tokensUpdated 1 mo ago
Auto-check: notes
PR Review Comments
giuseppe-trisciuoglio/developer-kit
Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line.
357 GitHub stars~1k tokensUpdated 1 mo ago
Auto-check: notes

Questions about Unit Test Service Layer

What does Unit Test Service Layer do?

Provides patterns for unit testing service layer with Mockito. Unit Test Service Layer is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides patterns for unit testing service layer with Mockito.

When should I use Unit Test Service Layer?

Unit Test Service Layer fits situations like: testing service behaviors and business logic without database; external services.

How do I install Unit Test Service Layer in Claude Code?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layer -a claude-code`. Or copy the skill folder (plugins/developer-kit-java/skills/unit-test-service-layer in giuseppe-trisciuoglio/developer-kit) into .claude/skills/unit-test-service-layer in your project. Claude Code loads it when a task matches its description.

How do I install Unit Test Service Layer in Codex?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layer -a codex`. Or copy the skill folder (plugins/developer-kit-java/skills/unit-test-service-layer in giuseppe-trisciuoglio/developer-kit) into .agents/skills/unit-test-service-layer in your project. Codex loads it when a task matches its description.

Can I use Unit Test Service Layer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/unit-test-service-layer, .gemini/skills/unit-test-service-layer, .github/skills/unit-test-service-layer and .opencode/skills/unit-test-service-layer in your project.

What does Unit Test Service Layer need to run?

Going by SKILL.md and its folder, Unit Test Service Layer needs the command-line tools its instructions call (mvn and gradle). Its frontmatter pre-approves these tools: Read, Write, Bash, Glob, Grep.

Does Unit Test Service Layer access the network?

SKILL.md names 3 domains. As links in the text: javadoc.io, junit.org and assertj.github.io. This is read from the text; nothing was executed.

Is Unit Test Service Layer safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Unit Test Service Layer use?

Unit Test Service Layer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Unit Test Service Layer use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.

What are the alternatives to Unit Test Service Layer?

Skills that share tags, products or a category with Unit Test Service Layer: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars), Go Testing (cxuu/golang-skills, 173 stars) and Contracts (samchon/nestia, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Unit Test Service Layer?

giuseppe-trisciuoglio (a GitHub user) maintains it in giuseppe-trisciuoglio/developer-kit, which has 357 GitHub stars. The repository holds 115 skills in this directory. The repository was last updated on September 10, 2026.

Source: giuseppe-trisciuoglio/developer-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Unit Test Service Layer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Unit Testing Service Layer with Mockito

Overview

When to Use

Instructions

1. Setup Test Class

2. Declare Mocks with @Mock and @InjectMocks

3. Arrange-Act-Assert with Validation

4. Test Exception Scenarios

5. Verify Complete Coverage

Examples

Basic Service Test Pattern

Verify Method Invocations

Best Practices

Constraints and Warnings

References

Files

Compare with similar skills

Similar skills

More from giuseppe-trisciuoglio/developer-kit

Related

Questions about Unit Test Service Layer

2. Declare Mocks with `@Mock` and `@InjectMocks`