mojo-test-runner

Execute Mojo tests with filtering and verbose output.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/mvillmow/ml-odyssey --skill mojo-test-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mojo-test-runner
Source: https://github.com/mvillmow/ml-odyssey/tree/main/.claude/skills/mojo-test-runner
Command: npx skills add https://github.com/mvillmow/ml-odyssey --skill mojo-test-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mojo-sdk, and includes scripts (resource) components.

What problem does it solve? This Skill provides a streamlined way to execute Mojo test files and suites, enabling developers to quickly verify code correctness, track test coverage, and support a Test-Driven Development (TDD) workflow. It automates test execution, saving manual effort.

Core Features & Use Cases:

  • Flexible Test Execution: Run all tests, specific files, or filter by test type (unit, integration, performance) for targeted testing.
  • Verbose Reporting: Get detailed output for each test run, aiding in quick debugging and understanding test failures.
  • Use Case: After making changes to your Mojo code, use this skill to run all unit tests. If any fail, quickly identify the issue, fix it, and re-run to ensure your changes haven't introduced regressions, maintaining code integrity.

Quick Start: Use the mojo-test-runner skill to run all Mojo tests in the 'tests' directory.

Frequently Asked Questions about mojo-test-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Mojo tests to verify my code works correctly?

Run Mojo tests using the mojo-test-runner to execute your test suite automatically. It runs all tests in your tests/ directory, specific files, or filtered by type (unit, integration, performance), providing detailed output to help you quickly identify and fix failures.

Can I run specific Mojo test files or filter tests by type?

Yes, mojo-test-runner supports running individual test files, filtering by test type (unit, integration, performance), or matching test patterns. This lets you target specific areas of your code without running the entire suite.

What happens if my Mojo tests fail—how do I debug?

The test runner provides verbose output for each test execution, capturing import errors, syntax errors, timeouts, and memory issues. This detailed reporting helps you quickly identify the root cause and fix problems before re-running tests.

Do I need to set up a specific directory structure for Mojo tests?

Yes, mojo-test-runner expects a tests/ directory in your repository and enforces Mojo naming conventions and test isolation. Your test files must follow these conventions for the runner to detect and execute them correctly.

Can I use mojo-test-runner for Test-Driven Development workflows?

Absolutely. The test runner automates test execution to support TDD workflows, letting you write tests first, run them frequently, and verify code correctness after each change, maintaining code integrity throughout development.