Home

Application Name	Developer	Made with	Rating	Last updated	Views	Installs
InterSystems Testing Manager for VS Code Use %UnitTest framework and Test Coverage Tool in VS Code	John Murray		4.5 (2)	21 Apr, 2026	984
irisapitester Docker microservice with InterSystems IRIS + Newman to test Apis	D Daniel Aguilar	Docker Python IPM	5.0 (2)	20 Sep, 2023	474
InterSystems Ideas Waiting to be Implemented Pull in all classes and tables called in a resource at export. I would like to see any utilized class, table, global variable, etc. that is utilized within a production component pulled into the export list when I export from that component. Right now, tables, XML message schemas, message classes, and others are not being pulled into the export list and it leads to missing classes when pushing components into production. It also requires a lot of extra documentation to be sure that all of the pieces I am building get moved as expected. V by Victoria Castillo 8 Votes 2 Comments Vote
iris-tripleslash Generate unit test cases from the class documentation	Henry Pereira	Docker IPM	5.0 (2)	13 Feb, 2023	575	27
iris-log-viewer iris-log-viewer provides an alternative web page	O Oliver Wilms	Docker Python IPM	4.7 (3)	11 Feb, 2023	632	23
interoperability-test Unit Test Interoperability production interface	O Oliver Wilms	Docker IPM	5.0 (1)	15 Sep, 2022	460	12
UnitTest_DTL_HL7 HL7 DTL TestCase Creator and Runner Framework	A Alex Woodhead		0.0 (0)	15 Aug, 2022	518
UnitTest_RuleSet Unit Tests for HL7 Routing in IRIS Integration	A Alex Woodhead		5.0 (1)	13 Jul, 2022	746
Adding tools in Studio Caché Intersystems Adding tools in Studio	T Tiago Ribeiro		2.0 (1)	15 Oct, 2018	236

InterSystems Testing Manager for VS Code

Use %UnitTest framework and Test Coverage Tool in VS Code

John Murray

4.5 (2)

21 Apr, 2026

984

irisapitester

Docker microservice with InterSystems IRIS + Newman to test Apis

D

Daniel Aguilar

Docker

Python

IPM

5.0 (2)

20 Sep, 2023

474

InterSystems Ideas Waiting to be Implemented

Pull in all classes and tables called in a resource at export.

I would like to see any utilized class, table, global variable, etc. that is utilized within a production component pulled into the export list when I export from that component. Right now, tables, XML message schemas, message classes, and others are not being pulled into the export list and it leads to missing classes when pushing components into production. It also requires a lot of extra documentation to be sure that all of the pieces I am building get moved as expected.

V

by Victoria Castillo