CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/qt-test-framework

Authors and runs Qt Test - the first-party C++ unit + GUI test framework that ships with Qt 6 (via the `QtTest` module header). Covers the `QTEST_MAIN` / `QTEST_APPLESS_MAIN` / `QTEST_GUILESS_MAIN` entry-point macros, the `QObject` private-slot test pattern, `QVERIFY` / `QCOMPARE` / `QFETCH` assertions, GUI event simulation (`QTest::mouseClick`, `QTest::keyClick`, `QTest::touchEvent`), `QSignalSpy` for signal introspection, `QBENCHMARK` for performance regression, and the `-o file,junitxml` CI output. Use for in-process testing of Qt widgets, QObject signal/slot chains, and Qt Quick / QML application logic; for out-of-process Qt-app driving, use an OS-native accessibility driver instead.

74

Quality

93%

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

86%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.

A well-structured, actionable skill body with executable examples throughout and a clean split of detailed reference material into one bundled file. Minor tightening of surrounding prose and an extra validation checkpoint would push it to full marks.

Suggestions

Trim prose that restates the code (e.g., the initTestCase/cleanupTestCase lifecycle sentence) to lift conciseness toward the lean anchor.

Add a brief verification checkpoint after the data-driven or GUI steps (analogous to Step 2's `-functions` check) to strengthen workflow_clarity.

Consider pulling the entry-point macro table or one inline benchmark snippet pointer to confirm the reference file is the only needed deep-dive, keeping the spine as the overview.

DimensionReasoningScore

Conciseness

Lean steps with code and no basic-concept padding, but some prose restates what is evident from the code (e.g., lifecycle slot descriptions), keeping it just below the fully-lean anchor.

4 / 5

Actionability

Provides copy-paste-ready executable CMake, C++ test classes, and bash run/CI commands covering the common author->run->parse cases.

5 / 5

Workflow Clarity

Ten well-sequenced steps with a strong validate+feedback loop in Step 2 and an anti-patterns checklist, but only one prominent explicit checkpoint across the workflow.

4 / 5

Progressive Disclosure

Clear overview and sectioned spine with the GUI/benchmark detail table split into a real, one-level-deep references/qt-gui-signal-benchmark.md that is clearly signaled in Steps 5, 7, and 10.

5 / 5

Total

18

/

20

Passed

Description

100%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.

A precise, third-person description that covers both what the skill does and when to use it, with an explicit negative boundary distinguishing it from sibling out-of-process drivers. Trigger terms are the natural vocabulary of the target user.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and APIs (entry-point macros, QVERIFY/QCOMPARE/QFETCH, GUI event simulation, QSignalSpy, QBENCHMARK, junitxml output) with comprehensive coverage of what the skill authors and runs.

5 / 5

Completeness

Explicitly answers 'what' (authors and runs Qt Test, covering enumerated macros and primitives) and 'when' via a concrete 'Use for in-process testing of …' clause plus a negative boundary for out-of-process driving.

5 / 5

Trigger Term Quality

Includes the natural terms users of this niche would say (Qt Test, Qt widgets, Qt Quick / QML, QObject signal/slot, QSignalSpy, QBENCHMARK) with synonyms, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (in-process Qt Test) and explicitly diverts out-of-process Qt-app driving to OS-native accessibility drivers, giving minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents