Great article, @Muhammad Waseem !

I'd add a docker command to start terminal.

First this one launches IRIS and creates a fresh namespace alone with the user 'demo' and password 'demo':

docker run --rm --name iris-demo -d -p 9091:1972 -p 9092:52773 -e IRIS_PASSWORD=demo -e IRIS_USERNAME=demo -e IRIS_NAMESPACE=DEV intersystemsdc/iris-community

Then to launch a terminal in PROD namespace:

docker exec -it iris-demo iris session iris -U DEV

DEV>

@Michael Davidovich , this is a good idea!

If you could provide a repo with legacy application inviting for dockerization I believe a lot of DC members could help.

Here is another video that updates the class and commits changes to the repo

Well, if you have git repo cloned with objectscript files and VSCode connected to IRIS all your files are imported into IRIS and can be executed there.

You change the objectscript files in VSCode, compile and they are imported into IRIS automatically.

VSCode and git maintain the versioning of changes for you.  

BTW,

this setting worked:

"intersystems.testingManager.client.relativeTestRoot": "/tests",

Now it sees them:

But they ask for ^UnitTest to be setup, instructions, etc.

Could it work similar as it works in IPM as @Timothy Leavitt demonstrated?

Because with IPM I can run tests all and standalone without any settings at all - it just works. 
Could the IPM be leveraged if it is presented in the repo/namespace?

Also you can create NAMESPACE/DATABASE via SQL. e.g.:

USER>:sql

SQL Command Line Shell

----------------------------------------------------


The command prefix is currently set to: <<nothing>>.

Enter <command>, 'q' to quit, '?' for help.

[SQL]USER>>Create Database TEST

1. Create Database TEST


0 Rows Affected

statement prepare time(s)/globals/cmds/disk: 0.0235s/2,162/14,045/0ms

          execute time(s)/globals/cmds/disk: 0.0843s/29,325/395,226/0ms

                          cached query class: %sqlcq.USER.cls21

---------------------------------------------------------------------------

[SQL]USER>>exit


USER>zn "TEST"


TEST>

HTH

Hi Gautam!

You can start from this template - it is a ready-made template that provides git, docker, ipm and unit-testing development environment.

Also you might be interested in ZPM Hub project by @Sergei Shutov 

Yes, just install it on IRIS and you'll have your own registry. Learn more.

Did it:

Now it likes it, but still the testing tool doesn't see any tests. Should it be absolute path or relative to the root of repo?

Do you mind to send a PR with a working setting to the repo?