test
Run unit tests, integration tests, or slow integration tests matching CI. Use to validate changes before submitting a PR.
88
82%
Does it follow best practices?
Impact
100%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
30%Add Unit Tests for the Metric Aggregation Component
Unit test conventions: JUnit 5, AssertJ, naming
JUnit 5 imports
100%
100%
AssertJ assertions
0%
100%
Correct file naming
100%
100%
No @Tag slow on unit test
100%
100%
JUnit 5 @Test annotation
100%
100%
Mockito usage
100%
100%
No JUnit 4 patterns
100%
100%
Exception assertion style
0%
100%
100%
3%Create a Developer Testing Cheatsheet for Apache SkyWalking
Correct Maven test commands and flags
Unit test command
75%
100%
Checkstyle skip in unit
100%
100%
Integration test command
100%
100%
skipUTs flag
100%
100%
excludedGroups=slow
100%
100%
Slow test command
100%
100%
ElasticSearchIT target
100%
100%
failsafe.failIfNoSpecifiedTests
100%
100%
Module path pattern
100%
100%
Default to unit
100%
100%
100%
3%Write an Integration Test for the SkyWalking Elasticsearch Storage Client
Integration test naming and @Tag("slow") convention
IT naming convention
100%
100%
@Tag slow annotation
100%
100%
JUnit 5 framework
100%
100%
AssertJ assertions
80%
100%
Correct package
100%
100%
No @Tag slow on non-slow tests
100%
100%
Mockito for mocking
100%
100%
No JUnit 4 lifecycle
100%
100%
- Repository
- apache/skywalking
- Commit
bf0fe4b
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.