I know we have a framework for having a test that runs a script and then compares the output with the expected output.
I haven't really wrapped my head around how. If I were going to do it (which makes a lot of sense in my Coverage++ effort) I would want to know where to put the script (/test/root/scripts) and the expected output (/test/root/scripts). What role do /test/root/data. images, relay and settings play? Are there file naming conventions to be followed? If I am reading CustomScriptTest correctly then I should be able to just drop in the script and expected output and my script will be run as a test, correct?
How do I set up the "mafia conditions" that would be part of the test environment? I've seen examples of adding items to inventory but how/where would I do that as part of the setup for CustomScriptTest? If I remember how to Mock instead of having a logged in character or comms with KoL where do I set it up for a script?
Is the answer write my own test and try not to break CST which is driven by directory contents?
Thanks.
I haven't really wrapped my head around how. If I were going to do it (which makes a lot of sense in my Coverage++ effort) I would want to know where to put the script (/test/root/scripts) and the expected output (/test/root/scripts). What role do /test/root/data. images, relay and settings play? Are there file naming conventions to be followed? If I am reading CustomScriptTest correctly then I should be able to just drop in the script and expected output and my script will be run as a test, correct?
How do I set up the "mafia conditions" that would be part of the test environment? I've seen examples of adding items to inventory but how/where would I do that as part of the setup for CustomScriptTest? If I remember how to Mock instead of having a logged in character or comms with KoL where do I set it up for a script?
Is the answer write my own test and try not to break CST which is driven by directory contents?
Thanks.