Run Tests
- 406 installs
- 113 repo stars
- Updated August 4, 2026
- coralogix/cx-cli
Run tests, lint, and formatting checks for the cx CLI Rust project using cargo test, cargo fmt, and cargo clippy.
About
Documents how to run and verify the cx CLI's Rust test suite, formatting, and clippy lint checks matching the CI sequence. A contributor uses it to verify code changes before committing or opening a PR.
- Full CI check: cargo fmt --check && cargo clippy --locked -- -D warnings && cargo test --locked
- Covers ignored integration tests and name-filtered runs
Run Tests by the numbers
- 406 all-time installs (skills.sh)
- Ranked #649 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/coralogix/cx-cli --skill run-testsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 406 |
|---|---|
| repo stars | ★ 113 |
| Last updated | August 4, 2026 |
| Repository | coralogix/cx-cli ↗ |
What it does
Run tests, lint, and formatting checks for the cx CLI Rust project using cargo test, cargo fmt, and cargo clippy.
Files
Run Tests & Verify
How to run tests, lint, and verify changes in the cx CLI. This skill covers running only - for writing new tests, see the add-command skill.
Quick Reference
| Command | What it does |
|---|---|
cargo test | Run all unit + integration tests |
cargo test <name> | Run tests matching a name substring |
cargo test -- --ignored | Run integration tests (filesystem-dependent, skipped by default) |
cargo fmt --check | Check formatting (no changes) |
cargo fmt | Auto-fix formatting |
cargo clippy --locked -- -D warnings | Lint with warnings-as-errors |
cargo build | Verify compilation |
Full CI Check
This is the exact sequence CI runs on every PR. Run it before committing or creating a PR:
cargo fmt --check && cargo clippy --locked -- -D warnings && cargo test --lockedThe --locked flag ensures the lockfile is respected - this matches .github/workflows/test.yml and lint.yml exactly. CI runs tests on Ubuntu, macOS, and Windows.
What to Run After a Change
Pick the right level of verification based on what changed:
- Any `.rs` file -
cargo test+cargo clippy --locked -- -D warnings - Formatting only -
cargo fmt --check(orcargo fmtto auto-fix) - `Cargo.toml` - full CI check (dependency changes affect everything)
- API types (`src/commands/<cmd>/api.rs`) - run that command's tests first (
cargo test alerts,cargo test dataprime), then the full suite - Test files only -
cargo test <relevant_test_name>
Running Specific Tests
Target tests efficiently instead of running the entire suite:
cargo test alerts- all tests with "alerts" in the namecargo test --test dataprime- only thetests/dataprime/integration test binary (input + output + query)cargo test --test dataprime input- only theinputsubmodule of that binarycargo test config::tests- only the tests in theconfigmodulecargo test metrics::tests- only metrics formatting tests
Interpreting Failures
Clippy warnings - treated as errors via -D warnings. Fix every warning before committing. Common ones: unused variables, unnecessary clones, missing error handling.
Format failures - run cargo fmt to auto-fix. These never need manual intervention.
Deserialization test failures - usually means struct field names don't match JSON keys. Check that #[serde(rename_all = "camelCase")] is on response types and that #[serde(default)] is on Vec fields (the API sometimes omits empty arrays).
Compilation errors in tests - likely caused by changing a public function signature. Check callers in both src/ and tests/ directories.
Integration test failures (`--ignored`) - these depend on filesystem state (~/.cx/ config directory). They may fail if the local environment isn't set up. This is expected in CI where no config exists.
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3k