Nice article @Hiroshi Sato !

Similar behavior can be achieved also with iris-cron-task app. 

Can be installed as:

USER>zpm "install iris-cron-task"

and used as the following (run every day at midnight with cron expression for the schedule):

USER>zw ##class(dc.cron.task).Start("IRIS cron task name","0 0 * * *","do ^Test",1,.taskId)

Hi @Stephen Canzano !

Unit tests are not included into the package when you publish it into repository. So when you install the package on a target machine only "solution" classes will be installed, not unit-tests.

E.g. here is csvgen app. I you check the source code it contains "solution" classes in src folder here and unit-tests in /tests folder.

module XML for csvgen has resources, that will be packaged while published in the IPM registry:

<Resource Name="community.PKG"/>

and the unittests, that are being used only development phase and can be imported to the system via load command:

<UnitTest Name="/tests" Package="community.csvgen.UnitTests" Phase="test"/>

So when you install csvgen package, e.g.:

USER>zpm "install csvgen" 

you'll see only RESOURCES classes installed.