DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to run the Kill Switch test suite after a code change with Kill Switch

Run cargo test to confirm the interpreter still passes its tests, with output for eval tests.

Short answer: Open a terminal in the repo folder after making your change; then run cargo test to run the full test suite; run cargo test eval::tests -- --show-output to run the evaluation tests and see their output. All steps.

Who it is forA contributor or maintainer who edited the Rust interpreter and needs to check nothing broke.

The problemWithout running tests, changes to the interpreter can break behavior without any visible sign.

The outcomeThe full test suite runs, and the evaluation tests print their output for review.

What you need first

  • A Rust toolchain with cargo installed
  • A terminal with access to the repo's files (clone of github.com/dom96/KillSwitch)
  • A web browser for reading SPEC.md and the benchmarks site, if you use those use cases

Steps

  1. Open a terminal in the repo folder after making your change.
  2. Run cargo test to run the full test suite.
  3. Run cargo test eval::tests -- --show-output to run the evaluation tests and see their output.
  4. Fix any failing test before you commit the change.

Prompt for your agent

In the dom96/KillSwitch repo, run `cargo test` and then `cargo test eval::tests -- --show-output`. Report the pass and fail counts and the names of any failing tests. Verify that no test fails before you suggest any commit.

Caveat. The README gives the test commands but does not describe what each test covers, so passing tests do not prove full correctness.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for dom96/KillSwitch and "Run the Kill Switch test suite after a code change"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer