Source profileQuality 73/100

affaan-m/ECC/docs/tr/skills/springboot-tdd/SKILL.md

springboot-tdd

Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

Source repository stars
234,327
Declared platforms
0
Static risk flags
0
Last source update
2026-07-27
Source checked
2026-07-28

Decision brief

What it does—and where it fits

80%+ kapsam (unit + integration) ile Spring Boot servisleri için TDD rehberi.

Best for

  • Use when adding features, fixing bugs, or refactoring.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/affaan-m/ECC --skill "docs/tr/skills/springboot-tdd"
Safe inspection promptEditorial

Inspect the Agent Skill "springboot-tdd" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/docs/tr/skills/springboot-tdd/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Ne Zaman Kullanılır

    Yeni özellikler veya endpoint'ler

    Yeni özellikler veya endpoint'lerBug düzeltmeleri veya refactoring'lerVeri erişim mantığı veya güvenlik kuralları ekleme
  2. 02

    İş Akışı

    1) Önce testleri yazın (başarısız olmalılar) 2) Geçmek için minimal kod uygulayın 3) Testleri yeşil tutarken refactor edin 4) Kapsamı zorlayın (JaCoCo)

    Önce testleri yazın (başarısız olmalılar)Geçmek için minimal kod uygulayınTestleri yeşil tutarken refactor edin
  3. 03

    Unit Testler (JUnit 5 + Mockito)

    Desenler: - Arrange-Act-Assert - Kısmi mock'lardan kaçının; açık stubbing tercih edin - Varyantlar için @ParameterizedTest kullanın

    Arrange-Act-AssertKısmi mock'lardan kaçının; açık stubbing tercih edinVaryantlar için @ParameterizedTest kullanın
  4. 04

    Web Katmanı Testleri (MockMvc)

    Review the “Web Katmanı Testleri (MockMvc)” section in the pinned source before continuing.

    Review and apply the “Web Katmanı Testleri (MockMvc)” source section.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score73/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars234,327SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
affaan-m/ECC
Skill path
docs/tr/skills/springboot-tdd/SKILL.md
Commit
4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

Spring Boot TDD İş Akışı

80%+ kapsam (unit + integration) ile Spring Boot servisleri için TDD rehberi.

Ne Zaman Kullanılır

  • Yeni özellikler veya endpoint'ler
  • Bug düzeltmeleri veya refactoring'ler
  • Veri erişim mantığı veya güvenlik kuralları ekleme

İş Akışı

  1. Önce testleri yazın (başarısız olmalılar)
  2. Geçmek için minimal kod uygulayın
  3. Testleri yeşil tutarken refactor edin
  4. Kapsamı zorlayın (JaCoCo)

Unit Testler (JUnit 5 + Mockito)

@ExtendWith(MockitoExtension.class)
class MarketServiceTest {
  @Mock MarketRepository repo;
  @InjectMocks MarketService service;

  @Test
  void createsMarket() {
    CreateMarketRequest req = new CreateMarketRequest("name", "desc", Instant.now(), List.of("cat"));
    when(repo.save(any())).thenAnswer(inv -> inv.getArgument(0));

    Market result = service.create(req);

    assertThat(result.name()).isEqualTo("name");
    verify(repo).save(any());
  }
}

Desenler:

  • Arrange-Act-Assert
  • Kısmi mock'lardan kaçının; açık stubbing tercih edin
  • Varyantlar için @ParameterizedTest kullanın

Web Katmanı Testleri (MockMvc)

@WebMvcTest(MarketController.class)
class MarketControllerTest {
  @Autowired MockMvc mockMvc;
  @MockBean MarketService marketService;

  @Test
  void returnsMarkets() throws Exception {
    when(marketService.list(any())).thenReturn(Page.empty());

    mockMvc.perform(get("/api/markets"))
        .andExpect(status().isOk())
        .andExpect(jsonPath("$.content").isArray());
  }
}

Entegrasyon Testleri (SpringBootTest)

@SpringBootTest
@AutoConfigureMockMvc
@ActiveProfiles("test")
class MarketIntegrationTest {
  @Autowired MockMvc mockMvc;

  @Test
  void createsMarket() throws Exception {
    mockMvc.perform(post("/api/markets")
        .contentType(MediaType.APPLICATION_JSON)
        .content("""
          {"name":"Test","description":"Desc","endDate":"2030-01-01T00:00:00Z","categories":["general"]}
        """))
      .andExpect(status().isCreated());
  }
}

Persistence Testleri (DataJpaTest)

@DataJpaTest
@AutoConfigureTestDatabase(replace = AutoConfigureTestDatabase.Replace.NONE)
@Import(TestContainersConfig.class)
class MarketRepositoryTest {
  @Autowired MarketRepository repo;

  @Test
  void savesAndFinds() {
    MarketEntity entity = new MarketEntity();
    entity.setName("Test");
    repo.save(entity);

    Optional<MarketEntity> found = repo.findByName("Test");
    assertThat(found).isPresent();
  }
}

Testcontainers

  • Production'ı yansıtmak için Postgres/Redis için yeniden kullanılabilir container'lar kullanın
  • JDBC URL'lerini Spring context'e enjekte etmek için @DynamicPropertySource ile bağlayın

Kapsam (JaCoCo)

Maven snippet:

<plugin>
  <groupId>org.jacoco</groupId>
  <artifactId>jacoco-maven-plugin</artifactId>
  <version>0.8.14</version>
  <executions>
    <execution>
      <goals><goal>prepare-agent</goal></goals>
    </execution>
    <execution>
      <id>report</id>
      <phase>verify</phase>
      <goals><goal>report</goal></goals>
    </execution>
  </executions>
</plugin>

Assertion'lar

  • Okunabilirlik için AssertJ'yi (assertThat) tercih edin
  • JSON yanıtları için jsonPath kullanın
  • Exception'lar için: assertThatThrownBy(...)

Test Veri Builder'ları

class MarketBuilder {
  private String name = "Test";
  MarketBuilder withName(String name) { this.name = name; return this; }
  Market build() { return new Market(null, name, MarketStatus.ACTIVE); }
}

CI Komutları

  • Maven: mvn -T 4 test veya mvn verify
  • Gradle: ./gradlew test jacocoTestReport

Unutmayın: Testleri hızlı, izole ve deterministik tutun. Uygulama detaylarını değil, davranışı test edin.

Alternatives

Compare before choosing