---
name: julialang-test-changes
description: "Run and update Julia tests after changing test files. Use when adding to or modifying any test file under test/ or stdlib/**/test/."
license: "MIT"
metadata:
  decimalai-skill-id: "1bcf1bab-486a-4701-8413-49ad6f9801dc"
  decimalai-version-id: "403102cc-4433-40d1-be9a-4385e302dd04"
  decimalai-version: "1"
  decimalai-body-sha256: "b45ff557efd575bde30d8b384787aceb33339535a63511114998f290ac7a2476"
  decimalai-name: "julialang/test-changes"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "testing"
  decimalai-source: "https://app.decimal.ai/s/julialang-test-changes@1/SKILL.md"
---
# Julia test changes

Use this when you change or add a Julia test.

- If you have changed a test (e.g. `foo`), run `make test-revise-foo` for the
  corresponding test to ensure that the test is still passing with your changes.
- If you are adding a new test, add it to an existing test file. Do not create a
  new test file unless explicitly instructed.
- Write one comment at the top of the test to explain what is being tested.
  Otherwise keep comments minimal.
- Use the environment variable `JULIA_TEST_FAILFAST=1` to make tests fail fast.
- Do not coordinate with fixed `sleep`s — loaded CI machines break any fixed
  delay. Synchronize on observable state (readiness markers, round-trips), or
  retry.