For debugging and testing it would be helpfull to disable starting / stopping magik sessions via robot variable.
Currently, start / stop a magik session using RobotMagikLauncher keywords are defined in init.robot files.
When debugging requires to work with an already started magik session (via manual opened remote_cli port) or to not close it afterwards for analysing , the init.robot file must be temporary renamed or its suite setup / teardown disable.
More comfortable would be keywords, wrapping the session start / stop and ask a robot variable (e.g. AUTO_START_MAGIK_SESSION) if the session should b started / stopped, before perform this.
For debugging and testing it would be helpfull to disable starting / stopping magik sessions via robot variable. Currently, start / stop a magik session using RobotMagikLauncher keywords are defined in init.robot files. When debugging requires to work with an already started magik session (via manual opened remote_cli port) or to not close it afterwards for analysing , the init.robot file must be temporary renamed or its suite setup / teardown disable.
More comfortable would be keywords, wrapping the session start / stop and ask a robot variable (e.g. AUTO_START_MAGIK_SESSION) if the session should b started / stopped, before perform this.