Software testing is an investigation conducted to provide stakeholders with information about the quality of the software product or service under test.
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 read a great article by @Timothy Leavitthere, where he wrote about unit testing and test coverage with ZPM. I am facing a slight problem and was wondering if someone has some insight into the matter.
Hi All, I was creating a unit test directory with the below script. But it not creating any directory as mentioned in code. I am working on MacBook with irisusr User as standard installation process.
if '$data(^UnitTestRoot) {
set mainFolder = "UnitTest\NewDir\"
set st = ##class(%File).CreateDirectoryChain(mainFolder _ testSuite)
if $$$ISOK(st) { set ^UnitTestRoot = mainFolder }
else {
write !, "UnitTestRoot folder could not be created. Consult with instructor."
How can I effectively unit test a Business Process Language(BPL) that incorporates three code activities calling methods from distinct ObjectScript classes?.
I'm trying to learn M programing for an Epic db class prerequisite. They said to download the IRIS Studio software to do the testing. I'm having a very difficult time finding information the language. I'm trying to run some examples that Epic has provided (like in below) but the compiler complains that it isn't valid. Of course, it doesn't tell you why it isn't valid.
By views