The testing/unit_tests folder now already includes tests for many functions (as of 5a65fe0). Ideally this should cover all functions (*.m files, except from those in the legacy and software folders). Here the progress is tracked. Some functions do not have their own tested, but are run when another function is tested. The tests are typically not comprehensive: they do not test all possible functionality (for instance different scenarios where different types of input are provided), but they are testing at least the most common use of each function.
Click here to show the list
Not sure whether these require tests, and whether it should be the _solution version that is tested:
The
testing/unit_testsfolder now already includes tests for many functions (as of 5a65fe0). Ideally this should cover all functions (*.mfiles, except from those in thelegacyandsoftwarefolders). Here the progress is tracked. Some functions do not have their own tested, but are run when another function is tested. The tests are typically not comprehensive: they do not test all possible functionality (for instance different scenarios where different types of input are provided), but they are testing at least the most common use of each function.Click here to show the list
addRxns)exportModel)exportToExcelFormat)addRxns)addRxns)solveLP)canConsume)copyToComps)checkModelStruct)importExcelModel)sortIdentifiers)importExcelModel)importExcelModel)getBlast)importExcelModel)importExcelModel)exportToExcelFormat)solveLP)solveLP)solveLP)Not sure whether these require tests, and whether it should be the
_solutionversion that is tested: