search

apjanke / octave-testify

New BIST (Built-In Self Test) functions for GNU Octave
GNU General Public License v3.0
4 stars 2 forks source link

Convenient way to run ".cc-test" tests from Octave built-ins #76

Open apjanke opened 5 years ago

apjanke commented 5 years ago

All these guys:

  <Octave/tests>/libinterp/corefcn/Cell.cc-tst ................ PASS      4/4
  <Octave/tests>/libinterp/corefcn/__contourc__.cc-tst ........ PASS      1/1
  <Octave/tests>/libinterp/corefcn/__dsearchn__.cc-tst ........ PASS      1/1
  <Octave/tests>/libinterp/corefcn/__ichol__.cc-tst ........... PASS      1/1
  <Octave/tests>/libinterp/corefcn/__ilu__.cc-tst ............. PASS      1/1
  <Octave/tests>/libinterp/corefcn/__lin_interpn__.cc-tst ..... PASS      1/1
  <Octave/tests>/libinterp/corefcn/__magick_read__.cc-tst ..... PASS      4/4

Need an easy way to reference and invoke them from test2.

apjanke commented 5 years ago

Okay, to do this, I probably need to factor out the logic add_octave_builtins and add_octave_standard_library from MultiBistRunner into a separate object that presents these directory structures as data, so they can be used for both MultiBistRunner's test population/discovery and test2's test name resolution.

Might also use that for abbreviating test locations for #77, if we associate each of those dir locations with an abbreviation, instead of just relying on matlabroot and relative-path logic.

apjanke commented 5 years ago

Should be able to call "fixed test scripts" directly, too. E.g. here's __run_test_suite__'s progress output:


Fixed test scripts:

  bug-35448.tst ............................................... PASS      2/2
  bug-35881.tst ............................................... PASS      1/1

If they're displayed unqualified, they should be able to be called unqualified. Though Octave itself does not support that:

>> test bug-35448.tst
????? bug-35448.tst does not exist in path
>>