test_run(): implement a "slave_options=.." option (for instance to use -noatomsautoload). Deprecate "mode_nw" "mode_nwni" and "mode_nwni_profiling" that are just particular cases
Reported by Samuel GOUGEON (@sgougeon)
BUG DESCRIPTION:
----------------
test_run(): Please
* Implement a "slave_options" option (for instance to use -noatomsautoload).
* Deprecate "mode_nw" "mode_nwni" and "mode_nwni_profiling" that are just particular cases.
Rationale:
---------
It is presently not possible to run slave sessions with all available Scilab launching options.
Only -nw, nwni and the -nwni -profiling combination are possible.
Yet, for instance it could be useful to prevent all autoloaded modules to be
actually autoloaded in the slave sessions. This is presently not possible.
We have to cancel the autoloading of all modules before running tests,
and then restore their autoloading status. Really unhandy.
We could imagine a new "noatomsautoload" option for test_run().
But multiplying specific options would be a bad way to proceed.
Instead, a unique "slave_options=..." would be much more relevant.
Then, all scilab launching options and combinations would become possible,
even for forthcoming options.
From there, the specific existing test_run() options "mode_nw", "mode_nwni"
and "mode_nwni_profiling" could be deprecated (with a warnobsolete() message).
They will be replaced with
"mode_nw" => "slave_options=-nw"
"mode_nwni" => "slave_options=-nwni"
"mode_nwni_profiling" => "slave_options=-nwni -profiling"
and "slave_options=-noatomsautoload -nw" will then become usable, for instance.