-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unit tests and demos #30
Comments
Actually, I maybe want to wait until I can do this in Matlab Unit Test framework style. The code for the tests is going to be too long to fit comfortably in BISTs. |
For 0.3.0, we'll do executable examples in lieu of a bunch of stuff explicitly structured as tests. |
Ah, looks like there's a Minor bummer: it requires the package to actually be installed; you can't just run it on an It calls printf ("Testing functions in package '%s':\n", files{i});
installed_pkgs_dirs = {installed_pkgs_lst{i}.dir, ...
installed_pkgs_lst{i}.archprefix};
installed_pkgs_dirs = ...
installed_pkgs_dirs (! cellfun (@isempty, installed_pkgs_dirs));
## For local installs installed_pkgs_dirs contains the same subdirs
installed_pkgs_dirs = unique (installed_pkgs_dirs);
if (! isempty (installed_pkgs_dirs))
## FIXME invoke another test routine once that is available.
## Until then __run_test_suite__.m will do the job fine enough
__run_test_suite__ ({installed_pkgs_dirs{:}}, {});
endif Bigger bummer: it doesn't find any of my BISTs.
|
Okay, looks like Reason the BISTs weren't being picked up is because they used You can now run the test suite with |
This package could use some tests (BISTs). For a bunch of stuff; there are hardly any tests at all.
Some demos would be nice too, both for demonstration purposes, and as a form of test.
The text was updated successfully, but these errors were encountered: