search

intersystems-community / intersystems-testingmanager

A VS Code extension to surface in the testing view any unit tests built with the InterSystems %UnitTest framework.
MIT License
2 stars 2 forks source link

InterSystems Testing Manager use a bad ^UnitTestRoot path #25

Closed damia13 closed 9 months ago

damia13 commented 9 months ago

Hello,

I use the "InterSystems Testing Manager" extension on a local iris instance in my vscode editor. I have a problem when i run unit test with vscode extension : the used path is bad.

In my namespace : ^UnitTestRoot="C:\git-data\care_backend\care_core\src\cls\core\test\services" VS code run test into : C:\git-data\care_backend\care_core\src\cls\core\test\services\daporrov\ daporrov is the username the instance. So, tests are running into a bad directory and i have one error "bad directory"

I don't know why the username is added at the end of the path. How to fix that ?

Thank you

gjsjohnmurray commented 9 months ago

Based on the instructions in the extension's README your ^UnitTestRoot node in namespace XXX should end with \XXX\UnitTestRoot (see step 2) and the prefix to this should match the Application Path you chose for the /_vscode web app you were told to create (see step 1).

When you are using the client-side paradigm to create and manage your unit test class sources, the extension doesn't load and run them directly from their source folder but first copies them to the {webAppPath}\XXX\UnitTestRoot\{username} folder. It does this in order to support remote IRIS servers as well as local ones.

damia13 commented 9 months ago

Thank you for these informations. It is work well.