Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

tester

Estrellas3

Forks0

Actualizado14 de julio de 2026 a las 17:07

Chords test and verification policy. Use for test authoring and verification strategy across core, proto, proto-values, client, the codegen runtime, and codegen correctness tests, including Gradle verification commands.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

SpineEventEngine

SpineEventEngine/Chords

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

Explorador de archivos

2 archivos

SKILL.md

readonly

name	tester
description	Chords test and verification policy. Use for test authoring and verification strategy across core, proto, proto-values, client, the codegen runtime, and codegen correctness tests, including Gradle verification commands.

Testing

Core Policy

Follow existing local style. Tests are named *Spec.kt and use JUnit Jupiter with Truth, AssertK, or Kotest matchers depending on the owning module; check neighboring tests before introducing a new dependency.
Put focused regression tests in the module that owns the behavior, under src/test/kotlin mirroring the production package.
Keep fixtures small and near the tests (Given.kt-style files), named after the behavior they represent.
Prefer public APIs, generated messages, and observable component state over private implementation details.
Cover both success and failure paths for validation, value parsing, extensions, and codegen output shape.
UI rendering and interaction are not covered by automated tests in this repository. Do not force UI snapshot tooling in; verify what is testable (logic, extensions, codegen) and report the manual-verification remainder explicitly.
Codegen behavior is verified end-to-end in codegen/tests (:codegen-tests), which runs generation against test Protobuf definitions and asserts on the generated API; add coverage there for generator changes.
Do not skip codegen-related Gradle tasks when generator behavior, Protobuf schemas, or generated API contracts are part of the change: rebuild codegen/plugins and run :codegen-tests:test so assertions run against freshly generated code, not outputs left over from a previous build.
Avoid tests that depend on a real Spine server, network resources, or local absolute paths.

Verification

Run the smallest useful command while iterating (repository root, JDK 11):

./gradlew :<module>:test
./gradlew :<module>:test --tests "io.spine.chords.proto.money.MoneyFieldSpec"
./gradlew :codegen-tests:test
./gradlew clean build

Module Gradle paths: core, proto, proto-values, client, runtime, codegen-tests. The codegen/plugins project verifies separately from codegen/plugins/ with JDK 17 (./gradlew build).

Follow the git-history and safety policy in AGENTS.md.

Más de este repositorio

mismo repositorio

build-engineer

SpineEventEngine/Chords

Chords build and release-engineering policy. Use for root and codegen/plugins Gradle build logic, buildSrc dependency coordinates, publishing wiring, version increments, generated `pom.xml`/`dependencies.md` reports, and the config submodule relationship.

2026-07-143

ci-engineer

SpineEventEngine/Chords

Chords CI/CD workflow guidance. Use for authoring or reviewing GitHub Actions workflows under `.github/workflows`: Ubuntu/Windows builds, license-report and version-increment guards, Gradle wrapper validation, and artifact publishing.

2026-07-143

code-reviewer

SpineEventEngine/Chords

Reviews Chords implementation changes for correctness, regressions, public API breaks, missing tests, and cross-module contract breaks. Use to review component, codegen, or build diffs. Read-only unless explicitly asked to run checks.

2026-07-143

codegen-engineer

SpineEventEngine/Chords

Chords code generation policy. Use for the ProtoData codegen plugins project, the codegen runtime library, generated MessageField/MessageOneof/MessageDef contracts, codegen correctness tests, and Protobuf declarations with Kotlin extensions in proto-values.

2026-07-143

component-engineer

SpineEventEngine/Chords

Chords UI component implementation policy. Use for the class-based component model, application shell, input components, layouts, message forms, validation display, dropdown/table/entity components, and server-connected components across the core, proto, and client modules.

2026-07-143

docs-reviewer

SpineEventEngine/Chords

Reviews Chords documentation changes: KDoc comments, README.md files, .agents/project.md, AGENTS.md, skills, command examples, and architecture or module maps. Read-only unless explicitly asked to run checks.

2026-07-143

Testing

Core Policy

Follow existing local style. Tests are named *Spec.kt and use JUnit Jupiter with Truth, AssertK, or Kotest matchers depending on the owning module; check neighboring tests before introducing a new dependency.

Put focused regression tests in the module that owns the behavior, under src/test/kotlin mirroring the production package.

Keep fixtures small and near the tests (Given.kt-style files), named after the behavior they represent.

Prefer public APIs, generated messages, and observable component state over private implementation details.

Cover both success and failure paths for validation, value parsing, extensions, and codegen output shape.

UI rendering and interaction are not covered by automated tests in this repository. Do not force UI snapshot tooling in; verify what is testable (logic, extensions, codegen) and report the manual-verification remainder explicitly.

Codegen behavior is verified end-to-end in codegen/tests (:codegen-tests), which runs generation against test Protobuf definitions and asserts on the generated API; add coverage there for generator changes.

Do not skip codegen-related Gradle tasks when generator behavior, Protobuf schemas, or generated API contracts are part of the change: rebuild codegen/plugins and run :codegen-tests:test so assertions run against freshly generated code, not outputs left over from a previous build.

Avoid tests that depend on a real Spine server, network resources, or local absolute paths.

Verification

Run the smallest useful command while iterating (repository root, JDK 11):

./gradlew :<module>:test ./gradlew :<module>:test --tests "io.spine.chords.proto.money.MoneyFieldSpec" ./gradlew :codegen-tests:test ./gradlew clean build

Module Gradle paths: core, proto, proto-values, client, runtime, codegen-tests. The codegen/plugins project verifies separately from codegen/plugins/ with JDK 17 (./gradlew build).

Follow the git-history and safety policy in AGENTS.md.