Well... after "MATUnit", "munit" and "Unit Testing Tools" another unit testing framework, which is not "unified" at all.
Tests are created with input / output vectors as well as one of three "comparators" and saved to a .mat-file. Then these .mat-files are sequently loaded to the workspace and the corresponding "component" is executed. This is error-prone, because the tests might influence each other, e.g. the component might read the workspace variables of a prior test, two tests might accidentally use the same .mat-file or even the component might overwrite the .mat-file of a test.
Furthermore there is no "assert", no concept like test method, test suite or the fixture, no way to check for expected exceptions, etc.
As I can't find the "model creation toolkit", the Simulink part isn't working at all.