Agent skill · Testing & QA

matlab-testing

Generate and run MATLAB unit tests using matlab.unittest and matlab.uitest. Parameterized tests, fixtures, mocking, coverage analysis, CI/CD with buildtool, app testing with gestures. Use when creating tests, writing test classes, running test suites, checking coverage, testing apps, or validating MATLAB code.

matlabgithub.com/matlabGitHub ↗
claude-codecodexcopilotNOASSERTION
Install
npx skills add matlab/matlab-agentic-toolkit --skill matlab-testing --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 9
SKILL.md size: 10 KB
Bundled scripts: none
Version: 1.1
Declared author: MathWorks
Path: skills-catalog/matlab-core/matlab-testing/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 868
Language: MATLAB

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Testing Generate, structure, and run MATLAB unit tests using the `matlab.unittest` framework. Covers class-based tests, parameterized testing, fixtures, mocking, coverage analysis, CI/CD integration, and app testing via MCP. ## When to Use - User asks to write tests for a MATLAB function or class - User wants to run an existing test suite - User needs coverage analysis or CI/CD configuration - Test-driven development — writing tests before implementation - Testing App Designer apps with programmatic gestures (see [reference/app-testing-guidance.md](reference/app-testing-guidance.md)) ## When NOT to Use - Testing Simulink models — use Simulink test skills - Performance benchmarking — use profiling workflows ## Must-Follow Rules - **Present a test plan first** — For non-trivial test suites, propose test methods and edge cases for user approval before writing code - **Always use class-based tests** — Every test file must inherit from `matlab.unittest.TestCase`. Never use script-based tests - **No logic in test methods** — No `if`, `switch`, `for`, or `try/catch`. Follow **Arrange-Act-Assert**. If a test needs conditionals, split into separate methods - **Test public interfaces, not

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Must-Follow Rules
  4. Workflow
  5. Simple tests (clear behavior, limited scope)
  6. Standard tests (large codebase, multiple files)
  7. Key Functions
  8. Qualification Levels
  9. Patterns
  10. Basic Test Class
  11. Parameterized Tests
  12. Setup, Teardown, and Fixtures
  13. Determinism
  14. Test Tags
Ships with 8 files
  • manifest.yaml
  • reference/app-testing-guidance.md
  • reference/constraints-guidance.md
  • reference/fixtures-guidance.md
  • reference/mocking-guidance.md
  • reference/parameterized-tests-guidance.md
  • reference/test-execution-guidance.md
  • scripts/printCoverageGaps.m
More from matlab-agentic-toolkit
All skills →
About this skill
What does the matlab-testing skill do?

Generate and run MATLAB unit tests using matlab.unittest and matlab.uitest. Parameterized tests, fixtures, mocking, coverage analysis, CI/CD with buildtool, app testing with gestures. Use when creating tests, writing test classes, running test suites, checking coverage, testing apps, or validating MATLAB code.

How do I install it?

Run `npx skills add matlab/matlab-agentic-toolkit --skill matlab-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From matlab/matlab-agentic-toolkit, a repository with 868 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going