It would be cool if, in the report output that listed test failures, it had a clickable link that would open the tested file in the editor and take you to the position of the failed test.
Doing this will probably take:
Tracking the file path and source file line number in BistBlock
Tracking individual errors in test2 and tying them to the failed BistBlocks
A detailed output form that listed each individual test block failure
Whatever formatting magic is used to make clickable links in the Octave Command Window
A test to see if we’re connected to the Command Window. This prob needs to go beyond isatty(), bc the CLI version of Octave doesn’t support this.
It would be cool if, in the report output that listed test failures, it had a clickable link that would open the tested file in the editor and take you to the position of the failed test.
Doing this will probably take:
BistBlocktest2and tying them to the failedBistBlocks