InterSystems Testing Manager - a new VS Code extension for the %UnitTest

Announcement

John Murray · May 22, 2023

Open Exchange

#Testing #Tools #Caché #InterSystems Ideas Portal #InterSystems IRIS #VSCode

If you have already built unit tests using the %UnitTest framework, or are thinking about doing so, please take a look at InterSystems Testing Manager.

Without leaving VS Code you can now browse your unit tests, run or debug them, and view previous run results.

InterSystems Testing Manager works with both of the source code location paradigms supported by the ObjectScript extension. Your unit test classes can either be mastered in VS Code's local filesystem (the 'client-side editing' paradigm) or in a server namespace ('server-side editing'). In both cases the actual test runs occur in a server namespace.

Feedback welcome.

Discussion (24)6

Evgeny Shvarov · May 22, 2023

Don't see it in Open Exchange :) Could you please publish?

0 0

Brett Saviano · May 22, 2023

@Evgeny Shvarov
It's available on the VS Code Marketplace, which is where people would expect to find it.

0 0

Evgeny Shvarov · May 22, 2023

Right, I'm not suggesting to remove it from there. But if you publish on Open Exchange it will let developers from InterSystems ecosystem it will help some developers to notice it.

1 0

Evgeny Shvarov · May 22, 2023

E.g. here on Open Exchange InterSystems can find dev tools and libs that could form their development environment.

1 0

John Murray · May 23, 2023

Now at https://openexchange.intersystems.com/package/InterSystems-Testing-Manag...

1 0

Evgeny Shvarov · Jun 6, 2023

Thank you!

0 0

Cameron Macintosh · May 23, 2023

This is awesome! I've really missed this from working in other programming languages.

According to the ReadMe (v0.2.0), this extension is currently considered a "Preview". Is there a product roadmap/timeline of what needs to be done to promote it out of "preview" status?

0 0

John Murray · May 23, 2023

Thanks for the positive response. IMO the main thing needed before the Preview tag gets dropped is feedback from %UnitTest users.

One motivation for publishing the Preview is the upcoming Global Summit, which I hope will be a good opportunity for in-person discussion about this extension and others. Find me at the George James Software booth in the Partner Pavilion.

0 0

John Murray · May 24, 2023

Also welcome are reviews, which can be posted on Marketplace and on Open Exchange.

1 0

Evgeny Shvarov · May 28, 2023

Tried with the project where I have ObjectScript Unittests. I call them manually with IPM and automatically with github workflow.

Testing manager is installed, I'm on a class with unit test.

Not sure though how it works?

0 0

Tani Frankel · May 28, 2023

@Evgeny Shvarov I believe the Market place link @John Murray provided has details of how to run the test (including some GIFs etc.)

https://marketplace.visualstudio.com/items?itemName=intersystems-communi...

0 0

John Murray · May 28, 2023

Since you are working client-side I think you need to set a intersystems.testingManager.client.relativeTestRoot setting to contain the workspace-relative path to the tests folder that's showing at the beginning of the breadcrumb in your screenshot.

Please see point 2 of https://github.com/intersystems-community/intersystems-testingmanager#wo...

0 0

John Murray · Jun 6, 2023

@Evgeny Shvarov
Did my suggestion help you get started with this extension?

0 0

Evgeny Shvarov · Jun 6, 2023

Hi @John Murray !

Not sure if I put it in a right place:

Says it shouldn't be here

0 0

John Murray · Jun 6, 2023

Move it outside the `objectscript.conn` object please.

0 0

Evgeny Shvarov · Jun 6, 2023

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?

0 0

John Murray · Jun 8, 2023

Please change this to a relative path (no leading slash).

Also, there was a bug in how it handled a "docker-compose" type of configuration.

Please try this dev build by downloading the zip, extracting the VSIX and dropping it into VS Code's Extensions view. If it works for you I will publish a new version to Marketplace.

1 0

Evgeny Shvarov · Jun 8, 2023

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?

0 0

John Murray · Jun 8, 2023

Thanks for confirming the fix. I'm publishing 0.2.1 now.

Please post enhancement ideas on the repo, for better tracking.

1 0

Evgeny Shvarov · Jun 8, 2023

BTW,

this setting worked:

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

1 0

Vadim Aniskin · Jul 25, 2023

An extension described in this announcement implements the idea Unit testing in VSCode | InterSystems Ideas
from the InterSystems Ideas Portal.

Thank you @John Murray for implementing this idea! 👏

1 0

John Murray · Aug 17, 2023

People interested in a better testing experience in VS Code may like to support this idea I posted recently:

https://ideas.intersystems.com/ideas/DPI-I-437

1 0

Vadim Aniskin · Aug 17, 2023

@John Murray
Thank you, great news, I just voted for your idea.

0 0

John Murray · Sep 15, 2023

We're starting to think about the next iteration of this extension. If you have any bug reports or enhancement requests please post them at https://github.com/intersystems-community/intersystems-testingmanager/is...

General questions or comments about the extension are also welcome on this DC thread.

0 0

InterSystems Testing Manager - a new VS Code extension for the %UnitTest framework