test execution -凯发k8网页登录
you can run many types of tests for your models, such as comparing test results to a baseline; comparing results between different matlab® releases; or running software-in-the loop (sil), hardware-in-the-loop (hil), or processor-in-the-loop (pil) generated code tests. to increase throughput for large test suites, iterations, and simulink® models, you can use parallel execution. collecting test coverage helps you assess the extensiveness of your tests and how completely the requirements are tested. to extend coverage, you can add test cases or generate test cases using simulink design verifier™. to debug tests and identify requirements not associated with a test, you can use the model slicer.
frequently viewed topics
categories
analyze dependencies, compare output to known values and across releases, run in parallel, and use external data input
run equivalence (back-to-back) tests for software-in-the-loop, processor-in-the-loop, and real-time hardware-in-the-loop
run tests on third-party asam® xil compliant test benches
run tests for integrated code, c code, and code from previous releases
view and analyze test results and test failures
evaluate and fix test failures and unexpected results
- check test coverage
implement, evaluate, and increase test coverage