Ryan Ollos

Here is the workaround I came up with for now. Define `packageName`, e.g. `mypackage.test`, then build up the test suite from the files in the package. There is probably a more straightforward way to implement something like this directly xunit, which I'll investigate when I have more time.

ts = TestSuite();
for i = 1:numel( fileName )
    fqClassName = [ packageName '.' fileName(i).name(1:end-2) ];
    if xunit.utils.isTestCaseSubclass( fqClassName )
        ts.add( TestSuite( fqClassName ) );
    end
end

ts.run();

Bug report: I have a package of tests, let's call it mypkg.tests. I run all of the tests in the package by typing `runtests mypkg.tests`. I have noticed that if there is a syntax error in one of the test classes, it will be silently skipped. However, if I run the test class by specifying the class explicitly, e.g. `runtests mypkg.tests.MyTestClass`, I see that the tests fail to run because of the syntax error. The syntax error can be an incorrect import statement, or something else equally likely to arise in practice. We have hundreds of tests and dozens of test classes, so this can cause problems for us that are not obvious.

There are several problems with this function:

1. printf statements are used rather than mexPrintf.
2. The output char array needs to be 1 greater in length.
3. Memory allocated to the output char array is deallocated before the function exits.

If anyone would like a working version, feel free to message me.