New method of running

[bdw429s]

OK, I have done an experiment to try and shave off about 4 seconds or so of startup time. Results may vary based on CPU power, etc. As much as I love the task runners and print helper, etc they rely on a bunch of modules that load up when CommandBox starts. I've changed the task component to a regular .cfm file that is directly invoked, bypassing the normal CommandBox bootstrap. I've also updated the readme to show how to call it now.

box -clishellpath=/path/to/TestRunner.cfm

All of the rest of the conventions as far as the test files and such should work the same. I just had to add a bit of boilerplate code to it to do what I needed. Please give this a try and see if it improves the execution time. I do think you'll need the absolute path to the testrunner.cfm file.

[kazk]

Thanks @bdw429s! I don't have numbers yet, but it seems much faster.
The only issue is that the exit code on failure/error doesn't seem to be set anymore.

[kazk]

3-4s speed up on my laptop 🚀
I'll let you know when this is deployed.

[bdw429s]

Sweet, sounds good.

[kazk]

Deployed