Hi Artem!

Very cool!

I've just tested it on docker (build a repo, see the PR) - and it works like a charm!

For docker funs it I set all the settings in Global during container building, so you just need to build a container and then you can run tests already.  

So git clone/download the repo and then run in the folder:

$ docker-compose -f "docker-compose.yml" up -d --build

Open IRIS terminal and run tests:

$ docker-compose exec iris iris session iris
USER>do ##class(DocumentTemplate.Test).RunAllTests("/iris/app/TestDocs")

Collect the results in /Results folder of the repo.  Tested on Mac OS with IRIS 2019.3 CE, store/intersystems/iris-community:2019.3.0.309.0

Ok, this is fair - we can remove the Best Practice tag for this. 

The idea was that this is important conversation if you consider internal guidelines on this for your organization and can take one approach from the best practices of experienced developers.

There is one exception though: if you are using some IRIS UI tools e.g. to develop productions you need to manage export/import these artefacts into files to let them be committed to Github then. Preferabbly automatically (e.g. per each Save operation).

@Yone Moreno , I assume it's an exercise. In that case, do you mind to share your code in a public repo and people will understand what you are going to achieve and will PR the answer. 

This is fixed in IRIS 2019.3 community version.

Image tag is store/intersystems/iris-community:2019.3.0.309.0