agentleFS
Sign inStart free
aviateskaviatesk/JETLS.jl/.agents/skills/run-test/SKILL.md

run-test

Skill319 starsChanged 11 days agoMITView on GitHub

Use when choosing or running JETLS tests after code changes. Prefer component-specific tests, avoid the full suite unless needed, and use TestRunner for focused iteration.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. apache/pinot★ 6.2ksame name
    2. UI5/openui5★ 3.3ksame name
    3. aviatesk/JET.jl★ 884same name
    4. 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 repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when you need to validate JETLS changes with tests or decide which test command to run.

    line 11
  2. Distinctive:

    When you changed a specific component, run the component-specific test instead of the full test suite.

    line 16
  3. Distinctive:

    Use this standard form:

    line 19

“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 JETLS tests

Use this skill when you need to validate JETLS changes with tests or decide which test command to run.

Choose the narrowest useful test

When you changed a specific component, run the component-specific test instead of the full test suite.

Use this standard form:

julia --startup-file=no --project=JETLSCore/test -e 'using Test; @testset "test_XXX" include("JETLSCore/test/test_XXX.jl")'

Notes:

  • --startup-file=no avoids loading unnecessary startup utilities.
  • --project=JETLSCore/test enables JETLS_TEST_MODE for proper test execution.

The tests of the jetls app commands are in test/ instead, e.g.:

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

Focused iteration with TestRunner.jl

For faster iteration on a specific @testset, use TestRunner.jl, which the test environment depends on:

julia --startup-file=no --project=JETLSCore/test -m TestRunner --verbose JETLSCore/test/test_XXX.jl "testset_name"

--project=JETLSCore/test before -m keeps JETLS_TEST_MODE enabled and resolves TestRunner through the shared workspace manifest, so the tests run with the TestRunner bundled in JETLS. Do not use the testrunner app shim: it loads its own TestRunner, which conflicts with the one JETLS imports.

TestRunner.jl is still experimental, but it is reliable enough to try first when the target @testset is clear. If it fails in a way that looks specific to TestRunner.jl, fall back to running the test file standalone.

Avoid the full suite by default

The full suite takes about 3.5 minutes as of June 2026:

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

Avoid it unless:

  • Changes affect multiple components.
  • The user explicitly requests the full test suite.
  • You are unsure which narrower tests are relevant.

Reporting

In the final response, report the exact test command you ran and whether it passed, failed, or timed out. If you skipped tests, 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.

Check your setup, free