You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a suggested enhancement that might be nice some day.
In addition to the informative validation results that are printed to the Matlab Command Window, it might be useful to write a results file using the Test Anything Protocol aka TAP. This would facilitate integration of the UnitTestToolbox with other testing tools that can read and display TAP results.
For example, Jenkins can read TAP results and display them nicely in a browser. Here's an example of what it looks like.
One option would be simply to add code to UnitTestToolbox that writes results in the TAP format.
Another option would be to get Matlab to generate the TAP output for us. Matlab will do this as part of its own testing framework. Here is an blog post about generating TAP results from a Matlab tests runner. Here is a testing utility from the ToolboxToolbox, based on the same blog post.
Although the second option would take care of writing the TAP output, it would require us to use Matlab's testing framework as the entry-point for testing, rather than the usual UnitTestToolbox functions. This might be a big, invasive change to make.
The text was updated successfully, but these errors were encountered:
This is a suggested enhancement that might be nice some day.
In addition to the informative validation results that are printed to the Matlab Command Window, it might be useful to write a results file using the Test Anything Protocol aka TAP. This would facilitate integration of the UnitTestToolbox with other testing tools that can read and display TAP results.
For example, Jenkins can read TAP results and display them nicely in a browser. Here's an example of what it looks like.
One option would be simply to add code to UnitTestToolbox that writes results in the TAP format.
Another option would be to get Matlab to generate the TAP output for us. Matlab will do this as part of its own testing framework. Here is an blog post about generating TAP results from a Matlab tests runner. Here is a testing utility from the ToolboxToolbox, based on the same blog post.
Although the second option would take care of writing the TAP output, it would require us to use Matlab's testing framework as the entry-point for testing, rather than the usual UnitTestToolbox functions. This might be a big, invasive change to make.
The text was updated successfully, but these errors were encountered: