St test

Skill mumez/smalltalk-dev-plugin/skills/st-test

Run SUnit tests in the running Pharo image. Use when verifying changes after import, or when checking results for a specific test class or package.From its SKILL.md

Install

npx -y skills add mumez/smalltalk-dev-plugin --skill st-test

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 407 tokens by cl100k_base, as published. Nobody here has run it

Run SUnit Tests

Execute SUnit tests after importing changes to Pharo.

Usage

/st-test TestClassName       # run a single test class
/st-test PackageName-Tests   # run all tests in a package

Steps

With arguments: run a specific test class or package

Determine whether the argument is a class name or a package name
- Class name (e.g. RsJsonTest) → call run_class_test
- Package name (e.g. RediStick-Json-Tests) → call run_package_test
Report pass/fail counts and any failures

Without arguments: run all test packages in the project

When no arguments are given, discover and run all test packages automatically:

Locate the source directory — read .project from the repository root and extract the srcDirectory value. Resolve it to an absolute path.
Identify test packages — find the BaselineOf package inside the source directory (a directory starting with BaselineOf) and read its BaselineOfXXX.class.st. Parse the baseline: spec method and collect all packages whose names end with -Tests (or follow the project's test-naming convention).
Check what is already imported — call list_packages to get the list of packages currently loaded in the Pharo image.
Run tests for imported packages — for each test package that is present in the image, call run_package_test and report the pass/fail results.
Report unimported packages — for any test package found in the BaselineOf but not loaded in the image, skip running tests and report it to the user with a note that they can run /st-import first to load it.

Examples

/st-test RsJsonTest
/st-test RediStick-Json-Tests

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most test skills give in 407 tokens

Counted across 1,201 of the 2,096 authors here whose files we hold, read 2026-09-06

Write a failing test before writing codein 43 of 1201, across 36 files
Run the full test suitein 36 of 1201, across 35 files
Test only one variable per experimentin 34 of 1201, across 17 files
Read product marketing context before asking questionsin 34 of 1201, across 14 files
Mock external dependenciesin 34 of 1201, across 30 files
Define primary, secondary, and guardrail metricsin 33 of 1201, across 16 files
Pre-determine sample size before startingin 31 of 1201, across 14 files
Test behavior rather than implementationin 31 of 1201, across 29 files
Formulate a hypothesis before designing a testin 30 of 1201, across 13 files
Document every test hypothesis, variant, and resultin 29 of 1201, across 11 files
Use descriptive test function namesin 25 of 1201, across 21 files
Commit to the methodology without stopping earlyin 24 of 1201, across 8 files

Said here and by no other author read

Determine if argument is class or package name
Call run_class_test for class names
Read .project to locate source directory
Identify test packages from BaselineOf
Call list_packages to check loaded packages
Run tests for all imported test packages

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.