원클릭으로 Manus에서 모든 스킬 실행

run-test

스타3

포크2

업데이트2026년 7월 3일 02:22

Run the slf4j-toys test suite with Maven. Use whenever you need to execute, verify, or debug tests in this repository — running the full suite, a single test class, or a single test method; checking whether a change broke anything before committing or pushing; or reproducing a failing test locally. Covers the two-tier build (core tests vs. the with-logback profile) and the exact mvnw invocations, including Java 21 and PowerShell argument-quoting requirements.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

useful-toys

useful-toys/slf4j-toys

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Running Tests in slf4j-toys

Why this skill exists

The project splits tests into two tiers so that IDEs keep a clean, conflict-free classpath while CI still gets full coverage. Getting the tier wrong either skips tests silently or fails to compile. Always pick the tier deliberately using the table below rather than guessing a command.

Guidelines

Always invoke Maven through the wrapper (.\mvnw), never a system-installed mvn — it pins the Maven version the project expects.
Default to plain test, not clean test — Maven's incremental compilation already picks up changed sources, so clean just costs a full recompile for no benefit. Only add clean if a run gives a suspicious result you suspect is stale build state; doc/build-execution-guide.md uses clean everywhere because it targets guaranteed-fresh CI/release builds, a different goal than this skill's iterative dev-loop runs.
Java 21 must be on PATH / JAVA_HOME before running any mvnw command. See powershell skill for how to set up JDK 21 in the current terminal session.
On PowerShell, wrap any -D parameter containing # (e.g. -Dtest=Class#method) in single quotes — PowerShell treats an unquoted # as a comment start and silently truncates the argument. See powershell skill for the full escaping rules.

Choosing a tier

slf4j-2.0 is activeByDefault, so plain .\mvnw test already runs under it; name it explicitly only alongside with-logback. Default to the core tier for everyday development. Reach for with-logback only when the change touches src/logback-main/java, src/logback-test/java, or anything under **/logback/** — those sources aren't on the default classpath at all, so core-tier tests can't exercise them.

Tier	Command	Tests	IDE run/debug/coverage
Core (default)	`.\mvnw test`	~1441	Yes
With Logback	`.\mvnw test -P slf4j-2.0,with-logback`	+84 (1525 total)	No — Maven only

# Core tier
.\mvnw test
.\mvnw test -Dtest=MeterLifeCycleTest
.\mvnw test '-Dtest=MeterLifeCycleTest#shouldCreateMeterWithLoggerInitialState'   # single quotes protect '#'

# With-Logback tier
.\mvnw test -P slf4j-2.0,with-logback
.\mvnw test -P slf4j-2.0,with-logback -Dtest=MessageHighlightConverterTest
.\mvnw test -P slf4j-2.0,with-logback '-Dtest=MessageHighlightConverterTest#testMsgStartMarker'

The with-logback profile adds the src/logback-main/java and src/logback-test/java source roots and swaps MockLogger for real logback-classic — the only way Logback converters and integration tests get compiled and run at all, since the IDE never imports those roots.

Related skills

powershell — JDK 21 setup and PowerShell argument-quoting details referenced above.
trunk-based-development — when to run which tier relative to commit/push/PR steps.

이 저장소의 다른 Skills

같은 저장소

create-issues

useful-toys/slf4j-toys

Create GitHub issues from AI-reported findings stored in the external findings directory (e.g., C:\git\slf4j-toys-findings\<analyzer>\<NN-scope>\). Use whenever converting analysis findings into trackable GitHub issues: reading finding files, extracting metadata into labels, creating issues via `gh issue create`, and closing resolved/accepted findings with resolution comments. Trigger on requests like "create issues", "convert findings to issues", "open GitHub issues", or any request to publish findings as repository issues — even when the word "issue" is not used explicitly.

2026-07-083

document-findings

useful-toys/slf4j-toys

Format and lifecycle for persisting analysis findings of slf4j-toys as Markdown files under an external findings directory (e.g., C:\git\slf4j-toys-findings\<analyzer>\<NN-scope>\). Use whenever saving new findings from a code review or audit, updating an existing finding (status change, fix validation, accepted-risk classification), renaming finding files with -accepted/-fixed suffixes, or maintaining the geral.md index. Trigger on requests like "guarde os achados", "documente as questões encontradas", "valide se o achado X foi corrigido", "marque como resolvido/aceito", or any request to record or revisit review results — even if the word "finding" is not used.

2026-07-083

update-wiki

useful-toys/slf4j-toys

Wiki synchronization workflow for slf4j-toys — cloning, updating, editing, committing, and pushing content to the GitHub wiki. Use whenever planning or coding behavior changes, new features, or architectural modifications that need to be reflected in the project wiki.

2026-07-083

trunk-based-development

useful-toys/slf4j-toys

Operational workflow for Trunk-Based Development in slf4j-toys — git worktrees, branch/worktree naming, commit and push gates, rebase-based sync, opening and merging PRs, cleaning up stale branches, and cutting releases. Use at the start of ANY code, test, build-config, or non-exempt documentation change in this repo — before writing the first line — to create the dedicated branch/worktree first (never edit directly on main); do not wait to be asked about git mechanics specifically. Trigger on the request's intent, not on git-specific wording: "fix this bug/issue/problem", "implement/add this feature", and "improve/refactor this" are all trunk-based-development triggers exactly like "create a branch for X" is — and so is starting to *plan* one of these (a fix, an improvement, a new feature), even before any code is written. This includes Plan Mode: read this skill the moment planning begins, not just before ExitPlanMode — the plan must account for branch/worktree creation as its first step from the outset, no

2026-07-043

code-review

useful-toys/slf4j-toys

Systematic code review and security audit methodology for slf4j-toys — analyzing Java packages for correctness, security, concurrency, design, performance, and style issues, and documenting findings as individual Markdown files under .findings/. Use whenever asked to review, audit, or analyze code for bugs, vulnerabilities, or quality issues. Covers finding categories and prefixes, file naming, per-finding Markdown structure, README index, and a principle-driven investigation approach that adapts to any code under review.

2026-07-033

git-commit-message

useful-toys/slf4j-toys

Writing conventions for Git commit messages in slf4j-toys — content only, not staging or pushing. Use whenever composing a commit message: the Conventional Commits header format (type(scope): summary), body structure, commit types and scopes, test-coverage mention, and AI attribution trailer. For staging/push/force-push mechanics and when to commit, see `trunk-based-development`; for passing a multi-line message through PowerShell, see `powershell`.

2026-07-033

name

run-test

description

Running Tests in slf4j-toys

Why this skill exists

Guidelines

Always invoke Maven through the wrapper (.\mvnw), never a system-installed mvn — it pins the Maven version the project expects.
Default to plain test, not clean test — Maven's incremental compilation already picks up changed sources, so clean just costs a full recompile for no benefit. Only add clean if a run gives a suspicious result you suspect is stale build state; doc/build-execution-guide.md uses clean everywhere because it targets guaranteed-fresh CI/release builds, a different goal than this skill's iterative dev-loop runs.
Java 21 must be on PATH / JAVA_HOME before running any mvnw command. See powershell skill for how to set up JDK 21 in the current terminal session.
On PowerShell, wrap any -D parameter containing # (e.g. -Dtest=Class#method) in single quotes — PowerShell treats an unquoted # as a comment start and silently truncates the argument. See powershell skill for the full escaping rules.

Choosing a tier

Tier	Command	Tests	IDE run/debug/coverage
Core (default)	`.\mvnw test`	~1441	Yes
With Logback	`.\mvnw test -P slf4j-2.0,with-logback`	+84 (1525 total)	No — Maven only

# Core tier
.\mvnw test
.\mvnw test -Dtest=MeterLifeCycleTest
.\mvnw test '-Dtest=MeterLifeCycleTest#shouldCreateMeterWithLoggerInitialState'   # single quotes protect '#'

# With-Logback tier
.\mvnw test -P slf4j-2.0,with-logback
.\mvnw test -P slf4j-2.0,with-logback -Dtest=MessageHighlightConverterTest
.\mvnw test -P slf4j-2.0,with-logback '-Dtest=MessageHighlightConverterTest#testMsgStartMarker'

Related skills

powershell — JDK 21 setup and PowerShell argument-quoting details referenced above.
trunk-based-development — when to run which tier relative to commit/push/PR steps.