#Testing

Continuing on the journey of implementing %UnitTest, @Timothy.Leavitt's Test Coverage package, and automated testing with Jenkins.

My question today: why do we utilize a unit test root directory?

I've been defining packages and classes to write unit tests as I've been developing and I run the tests on the command line or using a routine file that is setup as a debug target which has been working great. I use DebugRunTestCase() to do this (so the classes aren't deleted).

Are there any BDD testing automation implementations within Mumps/Cache Objects already in existence?

We are looking at using Cucumber for our Java regression test automation and would like to use similar feature file testing with the Cache code.

Looking to use something existing before building it.

Regards,
-Karl

Hi, colleagues!

Suppose you have large set of cubes, pivots and dashboards in your DeepSee solution.

Then you change the level, measure or dimension in the cube and is there any way to test that your new input didn't break current pivots, dashboards, etc?

How to test this?

How do you test your DeepSee solutions?

Hello,

I have a property which I need to move from one class definition to another as follows:

Old definition:

Class SCHED.SchedEntry
{
  
  Property Experiment as %String;

  Property ScanSlot as list of TracerEntry;

}

Class SCHED.TracerEntry
{
  
  Property Tracer As %String

}

I want to move the Experiment property to the TracerEntry class so that there is a different Experiment allowed for each ScanSlot, like this:

Did anyone run into this error when stopping a Production from Ens.Director?

Ens.Director::StopProduction => ERROR <Ens>ErrProductionNotQuiescent: IRIS can not become quiescent

It happens sporadically when an automated unit test from a class that extends %UnitTest.TestProduction runs a test on a Business Process. I already increased the parameter MAXWAIT to 30 seconds, but the error still happens.

Hi folks!

Those who actively use unittests with ObjectScript know that they are methods of instance but not classmethods.

Sometimes this is not very convenient. What I do now if I face that some test method fails I COPY(!) this method somewhere else as classmethod and run/debug it.

Is there a handy way to call the particular unittest method in terminal? And what is more important, a handy way to debug the test method?

Why do we have unittest methods as instance methods?

I want to test automatically that HL7 business operation works correctly in error conditions. One is to test CE acknowledgement. I have planned to implement test production which includes business services for different situations (AA, AE, CA, CE, timeout, late response etc).

How should I implement HL7 business service that always returns CE (commit error)? I have tried but it keeps returning "AA".

I was wondering if anyone has ever created a unit test which would run testing a mac routine (old fashion), via

We understand, unit testing in cache can be done with X Unit testing frameworks.

Can we automate unit testing in cache ? . Please let know

Hi all,

I am busy trying out the %UnitTest.TestProduction class to implement some automated production testing.

I have a scenario which I am not sure how to get the final results of for assertion. Below is the scenario I am trying to test, with comments on what I have done.

Greetings, can someone give me some help? I'm trying to use job for a instance method, as it's described here but...

Anyway, I have a method like this:

Hello everyone!

When running the command

do ##class(TestCoverage.Manager).RunTest(,"/nodelete",.userParams)

I now get the following error.

ERROR #5002 : ObjectScript error: <FUNCTION>zStart+45^%Monitor.System.LineByLine.1 <<==== **FAILED** TestCoverage.Manager:OnBeforeAllTests:::

These tests run fine in Studio.

I am trying to capture the write of a method to test the response in an unit test. I know everything works because one of my colleagues ran the code and did not froze on his machine.

I don't what is the cause of the freeze. I know that at line Use $io::("^"_$ZNAME) it stopes because i have put some write functions after every line in WriteCapture method and i only saw the first write function in terminal

I also used debug and in this case it didn't froze

We are successfully using System Default Settings to manage differences in settings across environments where the production and underlying code are otherwise identical. However, the TestingEnabled and LogGeneralTraceEvents settings don't appear to be settable via this mechanism. While we appear to be able to set them on the SDS page, they do not show up as selectable when resetting the settings on the Production Settings tab in the management portal - see screenshots below.