Token导航 LogoToken导航

Agent Skill · 前端设计

matlab-test-generator(matlab 测试生成器)

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

matlab-test-generator 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 6,835。

总安装 449周安装 18GitHub Stars 74下载 145核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:matlab-test-generator(matlab 测试生成器)
来源仓库:https://github.com/matlab/skills
仓库路径:skills/matlab-test-generator
安装命令:
npx skills add https://github.com/matlab/skills --skill matlab-test-generator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/matlab/skills --skill matlab-test-generator

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

matlab-test-generator 用于辅助测试设计、自动化测试和用例整理。适合编写单元测试、端到端测试和测试计划等测试场景。使用时需要确认项目测试框架和运行命令,避免为了通过测试而改坏真实逻辑;应区分本地模拟和测试环境。

通过 npx skills add 命令从 GitHub 仓库安装,需确认权限范围和维护状态。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/matlab-test-generator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/matlab/skills --skill matlab-test-generator;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

matlab-test-generator 怎么安装?

在终端执行 npx skills add https://github.com/matlab/skills --skill matlab-test-generator。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

matlab-test-generator 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

matlab-test-generator 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

matlab-test-generator 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

matlab-test-generator 用的人多吗?

公开数据是累计安装 449 次,近一周安装 18 次,下载 145 次,GitHub 74 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

matlab-test-generator 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
matlab-test-generator

matlab 测试生成器 · 本页

44974只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

MATLAB Test Generator

This skill provides comprehensive guidelines for creating robust unit tests using the MATLAB Testing Framework. Generate test classes, test methods, and test suites following MATLAB best practices.

When to Use This Skill

  • Creating unit tests for MATLAB functions or classes
  • Generating test suites for existing code
  • Writing test cases with assertions and fixtures
  • Creating parameterized tests
  • Setting up test environments with setup/teardown methods
  • When user requests testing, test coverage, or mentions unit tests

MATLAB Testing Framework Overview

MATLAB supports multiple testing approaches:

  1. Script-Based Tests - Simple test scripts with assertions
  2. Function-Based Tests - Test functions with local functions for each test
  3. Class-Based Tests - Full-featured test classes (recommended for complex testing)

Test Class Structure

Basic Test Class Template

classdef MyFunctionTest < matlab.unittest.TestCase
    % Tests for myFunction

    properties (TestParameter)
        % Define parameters for parameterized tests
    end

    properties
        % Test fixtures and shared data
    end

    methods (TestClassSetup)
        % Runs once before all tests
    end

    methods (TestClassTeardown)
        % Runs once after all tests
    end

    methods (TestMethodSetup)
        % Runs before each test method
    end

    methods (TestMethodTeardown)
        % Runs after each test method
    end

    methods (Test)
        % Individual test methods
    end
end

Critical Rules

File Naming

  • Test files MUST end with Test.m (e.g., myFunctionTest.m)
  • Class name must match filename
  • Follow PascalCase naming convention
  • Place in tests/ directory or alongside source with Test suffix

Test Method Naming

  • Use descriptive, readable names
  • Start with lowercase letter
  • Use camelCase
  • Describe what is being tested
  • Example: testAdditionWithPositiveNumbers

Assertions

Always use the appropriate assertion method:

  • verifyEqual(actual, expected) - Continues testing on failure
  • assertEqual(actual, expected) - Stops testing on failure (legacy)
  • verifyTrue(condition) - Verify boolean condition
  • verifyError(f, errorID) - Verify function throws error
  • verifyWarning(f, warningID) - Verify function issues warning
  • verifyInstanceOf(actual, expectedClass) - Verify object type
  • verifySize(actual, expectedSize) - Verify array size
  • verifyEmpty(actual) - Verify empty array

Complete Test Examples

Example 1: Testing a Simple Function

Function to test (add.m):

function result = add(a, b)
    % ADD Add two numbers
    result = a + b;
end

Test class (addTest.m):

classdef addTest < matlab.unittest.TestCase
    % Tests for add function

    methods (Test)
        function testAddPositiveNumbers(testCase)
            % Test addition of positive numbers
            result = add(2, 3);
            testCase.verifyEqual(result, 5);
        end

        function testAddNegativeNumbers(testCase)
            % Test addition of negative numbers
            result = add(-2, -3);
            testCase.verifyEqual(result, -5);
        end

        function testAddMixedNumbers(testCase)
            % Test addition of positive and negative
            result = add(5, -3);
            testCase.verifyEqual(result, 2);
        end

        function testAddZero(testCase)
            % Test addition with zero
            result = add(5, 0);
            testCase.verifyEqual(result, 5);
        end

        function testAddArrays(testCase)
            % Test element-wise addition of arrays
            result = add([1 2 3], [4 5 6]);
            testCase.verifyEqual(result, [5 7 9]);
        end
    end
end

Example 2: Parameterized Tests

classdef calculateAreaTest < matlab.unittest.TestCase
    % Tests for calculateArea function with parameters

    properties (TestParameter)
        rectangleDims = struct(...
            'small', struct('width', 2, 'height', 3, 'expected', 6), ...
            'large', struct('width', 10, 'height', 20, 'expected', 200), ...
            'unit', struct('width', 1, 'height', 1, 'expected', 1));
    end

    methods (Test)
        function testRectangleArea(testCase, rectangleDims)
            % Test rectangle area calculation
            area = calculateArea(rectangleDims.width, rectangleDims.height);
            testCase.verifyEqual(area, rectangleDims.expected);
        end
    end
end

Example 3: Tests with Fixtures

classdef DataProcessorTest < matlab.unittest.TestCase
    % Tests for DataProcessor class with setup/teardown

    properties
        TestData
        TempFile
    end

    methods (TestMethodSetup)
        function createTestData(testCase)
            % Create test data before each test
            testCase.TestData = rand(100, 5);
            testCase.TempFile = tempname;
        end
    end

    methods (TestMethodTeardown)
        function deleteTestData(testCase)
            % Clean up after each test
            if isfile(testCase.TempFile)
                delete(testCase.TempFile);
            end
        end
    end

    methods (Test)
        function testDataLoading(testCase)
            % Test data loading functionality
            save(testCase.TempFile, 'data', testCase.TestData);
            processor = DataProcessor(testCase.TempFile);
            testCase.verifyEqual(processor.data, testCase.TestData);
        end

        function testDataNormalization(testCase)
            % Test data normalization
            processor = DataProcessor();
            processor.data = testCase.TestData;
            normalized = processor.normalize();
            testCase.verifyLessThanOrEqual(max(normalized(:)), 1);
            testCase.verifyGreaterThanOrEqual(min(normalized(:)), 0);
        end
    end
end

Example 4: Error Testing

classdef validateInputTest < matlab.unittest.TestCase
    % Tests for validateInput function

    methods (Test)
        function testValidInput(testCase)
            % Test valid input passes
            testCase.verifyWarningFree(@() validateInput(5));
        end

        function testNegativeInputError(testCase)
            % Test negative input throws error
            testCase.verifyError(@() validateInput(-5), 'MATLAB:validators:mustBePositive');
        end

        function testNonNumericInputError(testCase)
            % Test non-numeric input throws error
            testCase.verifyError(@() validateInput('text'), 'MATLAB:validators:mustBeNumeric');
        end

        function testEmptyInputError(testCase)
            % Test empty input throws error
            testCase.verifyError(@() validateInput([]), 'MATLAB:validators:mustBeNonempty');
        end
    end
end

Test Organization Best Practices

Directory Structure

project/
├── src/
│   ├── myFunction.m
│   └── MyClass.m
└── tests/
    ├── myFunctionTest.m
    └── MyClassTest.m

Running Tests

Run all tests in directory:

results = runtests('tests')

Run specific test class:

results = runtests('myFunctionTest')

Run specific test method:

results = runtests('myFunctionTest/testAddPositiveNumbers')

Generate test suite:

suite = testsuite('tests');
results = run(suite);

With coverage report:

import matlab.unittest.TestRunner
import matlab.unittest.plugins.CodeCoveragePlugin

runner = TestRunner.withTextOutput;
runner.addPlugin(CodeCoveragePlugin.forFolder('src'));
results = runner.run(testsuite('tests'));

Assertion Tolerance

For floating-point comparisons, use tolerance:

% Absolute tolerance
testCase.verifyEqual(actual, expected, 'AbsTol', 1e-10);

% Relative tolerance
testCase.verifyEqual(actual, expected, 'RelTol', 1e-6);

% Both
testCase.verifyEqual(actual, expected, 'AbsTol', 1e-10, 'RelTol', 1e-6);

Test Assumptions

Use assumptions to skip tests when prerequisites aren't met:

function testPlotting(testCase)
    % Skip test if not running in graphical environment
    testCase.assumeTrue(usejava('desktop'), 'Requires desktop environment');

    % Test code here
    fig = figure;
    plot(1:10);
    testCase.verifyInstanceOf(fig, 'matlab.ui.Figure');
    close(fig);
end

Test Tagging

Tag tests for selective execution:

methods (Test, TestTags = {'Unit'})
    function testBasicOperation(testCase)
        % Fast unit test
    end
end

methods (Test, TestTags = {'Integration', 'Slow'})
    function testDatabaseConnection(testCase)
        % Slower integration test
    end
end

Run tagged tests:

% Run only Unit tests
suite = testsuite('tests', 'Tag', 'Unit');
results = run(suite);

Mock Objects and Stubs

For testing code with dependencies:

function testWithMock(testCase)
    % Create mock object
    import matlab.mock.TestCase
    [mock, behavior] = testCase.createMock(?MyInterface);

    % Define behavior
    testCase.assignOutputsWhen(withAnyInputs(behavior.methodName), expectedOutput);

    % Use mock in test
    result = functionUnderTest(mock);
    testCase.verifyEqual(result, expectedValue);
end

Performance Testing

Test execution time:

function testPerformance(testCase)
    % Test function executes within time limit
    tic;
    result = expensiveFunction(largeData);
    elapsedTime = toc;

    testCase.verifyLessThan(elapsedTime, 1.0, ...
        'Function should complete within 1 second');
end

Checklist for Test Creation

Before finalizing tests, verify:

  • Test file ends with Test.m
  • Class inherits from matlab.unittest.TestCase
  • Test methods use descriptive names
  • Appropriate assertions used (verify vs assert)
  • Edge cases covered (empty, zero, negative, large values)
  • Error cases tested with verifyError
  • Floating-point comparisons use tolerance
  • Setup/teardown methods clean up resources
  • Tests are independent (can run in any order)
  • Tests follow Arrange-Act-Assert pattern
  • Parameterized tests used for similar test cases
  • Comments explain what is being tested

Common Patterns

Arrange-Act-Assert Pattern

function testCalculation(testCase)
    % Arrange - Set up test data
    input1 = 5;
    input2 = 3;
    expected = 8;

    % Act - Execute the code under test
    actual = myFunction(input1, input2);

    % Assert - Verify the result
    testCase.verifyEqual(actual, expected);
end

Testing Private Methods

% Use access to test private methods
classdef MyClassTest < matlab.unittest.TestCase
    methods (Test)
        function testPrivateMethod(testCase)
            obj = MyClass();
            % Access private method
            result = obj.privateMethod(testCase);
            testCase.verifyEqual(result, expectedValue);
        end
    end
end

Testing Static Methods

function testStaticMethod(testCase)
    % Test static method without instantiation
    result = MyClass.staticMethod(input);
    testCase.verifyEqual(result, expected);
end

Troubleshooting

Issue: Tests not discovered

  • Solution: Ensure filename ends with Test.m and class inherits from matlab.unittest.TestCase

Issue: Floating-point comparison failures

  • Solution: Use 'AbsTol' or 'RelTol' parameters with verifyEqual

Issue: Tests affecting each other

  • Solution: Ensure proper cleanup in teardown methods and test independence

Issue: Slow test execution

  • Solution: Use tags to separate fast unit tests from slow integration tests

Additional Resources

  • Use doc matlab.unittest.TestCase for complete assertion reference
  • Use doc matlab.unittest.fixtures for advanced fixture usage
  • Use doc matlab.mock for mocking framework documentation

平台分布

Codex

33.98%
按下载量换算49

Claude

29.29%
按下载量换算42

Cursor

17.98%
按下载量换算26

Gemini CLI

9.8%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills