CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/jqwik-testing

Use for any question about property-based or generated-input tests in Java or Kotlin, including quick how-to questions, invariants like commutativity or adding zero, and edge cases nobody thought of: jqwik on JUnit 5 with @Property, @ForAll, Arbitraries, @Provide generators, shrinking and statistics.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a well-sequenced install-to-CI tutorial with mostly copy-paste-ready snippets at every step, and it correctly externalizes bulk lookup tables into a single one-level-deep reference file that exists in the bundle. Code is executable with minor gaps (undefined `mapper`, the unsupported `@Statistics` annotation), and a few comparative asides plus a hardcoded version number keep conciseness just short of lean.

Suggestions

Fix the Step 6 statistics example: drop the unsupported `@Statistics` method annotation and rely on `Statistics.label("evenness").collect(...)` alone, and define `mapper` in Step 4 so both snippets are copy-paste runnable.

Trim comparative asides ("more than Hypothesis's 100 or proptest's 256") and the platform-integration parentheticals.

Move the pinned jqwik version fully into the reference's version note (e.g., "see references/jqwik-reference.md for the current version") so the body's build snippets don't drift as the version ages.

DimensionReasoningScore

Conciseness

The body is code-heavy and mostly lean, with jqwik-specific API details that are genuinely additive rather than generic-concept padding. A few asides could be trimmed — "more than Hypothesis's 100 or proptest's 256", "The @Property annotation marks a property test (JUnit 5 hooks in via the platform)" — and the time-sensitive version "1.9.3" is hardcoded in two build snippets, matching anchor 4 rather than a fully lean 5.

4 / 5

Actionability

Provides copy-paste Maven XML, a Gradle block, complete Java property examples, a configuration field table, and CI commands covering the common cases. Minor gaps keep it at anchor 4: the Step 4 example references an undefined `mapper` field, and the Step 6 `@Statistics` method annotation is not part of jqwik's API (statistics are collected via `Statistics.label(...).collect(...)` calls), so that snippet will not compile as written.

4 / 5

Workflow Clarity

Steps 1-8 form a coherent install → write → constrain → customize → observe → configure → CI sequence, each with concrete code; as a non-destructive library-adoption skill no validation cap applies. Verification is implicit until Step 8 ("mvn test # runs JUnit 5 tests including @Property") with no intermediate checkpoints, matching anchor 4's "clear sequence with most checkpoints present".

4 / 5

Progressive Disclosure

The body keeps quick-start content inline while pushing lookup tables (constraint annotations, Arbitraries catalog, anti-patterns, limitations, version note) into a single real bundle file, references/jqwik-reference.md, cited five times with each mention signaling exactly what it contains ("Full table:", "Half-bounded generators, sets, maps, and subsetOf:"). References are one level deep and easy to navigate, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is highly specific, naming jqwik's JUnit 5 integration, its core API features, and concrete invariant examples, with an explicit "Use for" trigger clause covering Java/Kotlin property-based and generated-input testing. All four dimensions land at 4: the trigger guidance and niche distinctiveness are strong, but the skill's actions are implied via a topic list rather than stated with verbs, and a few natural synonyms are absent.

Suggestions

Lead with an action-verb statement of what the skill does (e.g., "Write and debug jqwik property tests on JUnit 5: ...") so the 'what' is as explicit as the 'Use for...' when-clause.

Add natural synonyms such as "generative testing", "QuickCheck-style tests", or plain "property testing" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names several concrete elements — "jqwik on JUnit 5 with @Property, @ForAll, Arbitraries, @Provide generators, shrinking and statistics" and "invariants like commutativity or adding zero" — matching the anchor for several specific actions with minor gaps. It falls short of 5 because capabilities are given as a topic list rather than comprehensive action-verb statements (build integration, Kotlin setup, lifecycle hooks are absent).

4 / 5

Completeness

The "when" is explicit and rich ("Use for any question about property-based or generated-input tests in Java or Kotlin, including quick how-to questions..."), and the "what" is present via "jqwik on JUnit 5 with @Property, @ForAll, Arbitraries...". It matches anchor 4 rather than 5 because the what-side is a noun-phrase topic list, not concrete statements of what the skill does.

4 / 5

Trigger Term Quality

Includes natural phrases users would say — "property-based", "generated-input tests", "Java or Kotlin", "jqwik", "invariants", "edge cases" — plus the annotation names a user might quote. A few natural synonyms ("generative testing", "QuickCheck", plain "property testing") are missing, so it fits anchor 4 rather than the comprehensive coverage of 5.

4 / 5

Distinctiveness Conflict Risk

Pins a clear JVM niche with jqwik-specific triggers (@Property, @ForAll, Arbitraries), but "any question about property-based or generated-input tests in Java or Kotlin" claims territory that could also match the quickcheck-testing sibling (e.g., JUnit-QuickCheck questions). Minor overlap with a closely related skill fits anchor 4; the explicit jqwik naming keeps it above 3.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page