agentleFS
aviateskaviatesk/JET.jl/.agents/skills/run-test/SKILL.md

run-test

Skill884 starsChanged 4 months agoMITView on GitHub

Use when choosing or running JET tests after code changes. Prefer the most specific relevant test, use TestRunner for focused iteration, and reserve the full suite for broad validation.

4 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. aviatesk/JETLS.jl★ 31911% same

    Wrote their own version · 3

    1. apache/pinot★ 6.2ksame name
    2. UI5/openui5★ 3.3ksame name
    3. mx-space/core★ 567same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when validating JET changes or deciding which test command to run.

    line 11
  2. Very specific:

    If the user names a test file or testset, run it first.

    line 16
  3. Distinctive:

    Run commands from the repository root so relative paths and the workspace resolve correctly.

    line 28
  4. Very specific:

    Follow test/runtests.jl rather than assuming every test has a root-level path.

    line 39
  5. Very specific:

    When testrunner --help succeeds and the target @testset is clear, use TestRunner.jl for faster iteration:

    line 43
  6. Distinctive:

    Avoid the full suite unless:

    line 57
  7. Distinctive:

    No narrower test provides sufficient coverage.

    line 61
  8. Distinctive:

    Use the package test lifecycle when matching CI or performing final broad validation:

    line 63
  9. Very specific:

    If a failure looks environment-related, first confirm that the command ran from the repository root.

    line 78

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run JET tests

Use this skill when validating JET changes or deciding which test command to run.

Choose the narrowest useful test

If the user names a test file or testset, run it first. Otherwise, use test/runtests.jl and nearby tests to identify the smallest relevant target.

Most test files can run independently. For example:

julia --startup-file=no --project=test test/ui/test_print.jl
  • --startup-file=no avoids loading unrelated startup utilities.
  • --project=test selects JET's test environment and its dependencies.
  • Run commands from the repository root so relative paths and the workspace resolve correctly.

JET tests are organized by component. Common locations include:

  • test/abstractinterpret/
  • test/analyzers/
  • test/toplevel/
  • test/ui/

There are also integration and miscellaneous tests directly under test/. Follow test/runtests.jl rather than assuming every test has a root-level path.

Focused iteration with TestRunner.jl

When testrunner --help succeeds and the target @testset is clear, use TestRunner.jl for faster iteration:

testrunner --project=test \
  test/toplevel/test_virtualprocess.jl \
  "syntax error reports"

TestRunner.jl is experimental. If it fails for a TestRunner-specific reason, fall back to running the complete test file independently.

Full-suite validation

Avoid the full suite unless:

  • Changes affect multiple components or shared compiler infrastructure.
  • The user explicitly requests it.
  • No narrower test provides sufficient coverage.

Use the package test lifecycle when matching CI or performing final broad validation:

julia --startup-file=no -e 'using Pkg; Pkg.test()'

JET's workspace also supports running test/runtests.jl directly:

julia --startup-file=no --project=test test/runtests.jl

Environment failures

If a failure looks environment-related, first confirm that the command ran from the repository root. Do not modify Project.toml or test/Project.toml to fix the environment. Report the unresolved failure and ask the user for guidance.

Reporting

In the final response, report the exact command that ran and whether it passed, failed, or timed out. If tests were skipped, explain why.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.