matlab-testinglisted

# 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 implementation** — Never test private methods directly - **Execute via MCP** — Use `run_matlab_test_file` or `evaluate_matlab_code` to run tests ## Workflow ### Simple tests (clear behavior, limited scope) 1. Briefly state what you'll test (methods + key edge cases) 2. Write the test file a