Re: RPGUnit vs ILEUnit

In my excitement, I overlooked the create command in the instructions. We have a custom compile command, so I tried to simply set the *SRVPGM object description to "RPGUNIT". That got me past that hurdle.

Then I had *JOBD issues. I got around that by setting the *LIBL in the prefs to be *CURRENT. I got a test to run but then ran out of time.


Thanks




-----Original Message-----
From: Thomas Raddatz [mailto:thomas.raddatz@xxxxxx]
Sent: Friday, March 09, 2018 2:17 AM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: Re: RPGUnit vs ILEUnit

What utility did you use to create the service program? Did you create it by hand?

The iRPGUnit plug-in provides 2 mechanisms for checking a service program to be a unit test suite.

By default it looks a the text description of the service program and checks whether it starts with "RPGUNIT" ignoring the case of the letters.

The second option is check whether the user defined attribute of the service program is set to "RPGUNIT".

So if you created the service program by hand, most likely non of these tests will succeed.

If you like you can disable the test on the iRPGUnit preference page. Just set option "Check test suite service program" to "*NONE".

From the iRPGUnit help text:

"Check test suite service program
Specifies whether or not to validate the test suite service program.

The possible values are:

*NONE : Service programs are not validated when selected for execution.
*TEXT : The object description of the selected service program must start with 'RPGUnit' (case insensitive).
*ATTRIBUTE : The user defined attribute of the service program is checked for 'RPGUnit' (case insensitive). That is the preferred option, but does not work for all RDi versions. See APAR SE55976 for details.

The user defined attribute of the test suite service program is automatically set to 'RPGUNIT', when the service program is created by RUCRTTST. "

- Thomas.