Validation

Validation and testing

ISETBio uses ISETCam's shared test engine and reporting tools (TestSuite, TestRunner, ieTestReport). Testing runs through the current subsystem and repository runners in validate/, not the retired isetvalidate/RemoteDataToolbox/UnitTestToolbox infrastructure this page used to describe.

results = isetbioUnitTest;          % core unit suite
results = isetbioUnitTest('full');  % includes FullOnly tests

results = conesUnitTest;            % focused subsystem examples
results = eyemovementUnitTest;
results = opticalimageUnitTest;

Tutorial and example scripts have their own runners, which discover t_* and s_* files:

tutorialRun = isetbioTutorialTest;
exampleRun  = isetbioExampleTest;

run = isetbioTutorialTest('selection', 't_cMosaicBasic');
run = isetbioExampleTest('selection', 's_matlabConv2');

A script that is deliberately resource-heavy or interactive can be discovered but skipped with a % SkipFile comment; skipped scripts are still useful reading material, but the routine test runner does not execute them. See Guided tutorials for which current tutorials carry this marker.

Runs save checkpoint.mat, progress.log, and planned-files.txt under a timestamped directory in local/. Report a completed or interrupted run with:

ieTestReport(run, 'List', {'failed', 'skipped'});

For test authoring conventions (colocated _tests_ directories, test_<subject>.m naming, focused subsystem runners), see the matlab-testing skill in the ISETBio repository.