SAS 9.4 Support

[Amit]

I am trying to implement it on SAS 9.4. I have made following changes and the script is running without an error but the final report test_doc_en.html is not getting generated. Please help.

Changes:
0.
Required version changes and path changes in files sasunit.9.4.windows.en.cfg, sasunit.9.4.windows.en.cmd, and sasunit.9.4.windows.en.overwrite.cmd

1. Commented "check SAS version" condition in initsasunit.sas
   %IF %_sasunit_handleError( &l_macname
   , WrongVer
   , (&sysver. NE 9.1) AND (&sysver. NE 9.2) AND (&sysver. NE 9.3)
   , Invalid SAS version - only SAS 9.1 to 9.3)
   %THEN %GOTO errexit;

2. Commented "if test coverage should be assessed: check SAS version" condition in initsasunit.sas
   %IF %_sasunit_handleError( &l_macname
   , WrongTcVer
   , &sysver. NE 9.3
   , Invalid SAS version for test coverage assessment - only 9.3 supported)
   %THEN %GOTO errexit;

3. Provided complete path to all required parameters to macro call "initSASUnit" in run_all.sas

I am running tests on windows machine.

[Klaus Landwich]

Hi Amit,

I appreciate that you're trying to port SASUnit to SAS9.4. What you did should be sufficient. Without further information on what went wrong, I can't help you.

Would you be so kind to e-mail me your run_all.log.
You'll find it in your sasunit target folder. You specify this folder with parameter io_target in initSASUnit.

Are you currently trying to run the example project? Or do you port an existing project of yours to SAS 9.4?

Looking forward to your response.

Regards
Klaus

mailto: klandwich@users.sf.net

[Amit]

Hi Klaus,

I have just sent you the log from amitnakrani82@gmail.com.
I am trying to run example project only.

Please refer to the email and suggest me.

Regards,
Amit

[Andreas Mangold]

Support for SAS 9.4 is now available in Version 1.3 of SASUnit.

[kacperdominik]

Hello,

I followed your instructions for the attached example and I don't see correct results in the HTML report. Program finished with errors.

I am using:

SAS 9.4 on x64 machine (Windows). I have the newest version of Doxygen.

Firstly, I changed the paths in all configuration files:

from "C:\Program Files\SASHome2" to "C:\Program Files\SASHome".

Then, I ran:

sasunit.9.4.windows.en.overwrite.cmd

In the command prompt, I saw the following message:

Exit code: 2
SAS ended with errors! Check run_all.log for details!

1. In the log, I see the following error:

MPRINT(REPORTAUTONHTML): FILENAME allfiles
"D:\sasunit\example\doc\sasunit\en/log/*.tcg";
MPRINT(_REPORTAUTONHTML): DATA _null;
MPRINT(_REPORTAUTONHTML): INFILE allfiles end=done dlm=',';
MPRINT(_REPORTAUTONHTML): FILE "D:\sasunit\example\doc\sasunit\en/log/000.tcg";
MPRINT(_REPORTAUTONHTML): INPUT row :$256.;
MPRINT(_REPORTAUTONHTML): PUT row;
MPRINT(_REPORTAUTONHTML): RUN;

ERROR: Physical file does not exist, D:\sasunit\example\doc\sasunit\en\log*.tcg.
NOTE: The file "D:\sasunit\example\doc\sasunit\en/log/000.tcg" is:
Filename=D:\sasunit\example\doc\sasunit\en\log\000.tcg,
RECFM=V,LRECL=32767,File Size (bytes)=0,

I attach full log.

1. HTML reports does not look good (in comparison to originally attached).

   I attach screenshot

[Klaus Landwich]

Hello kacperdominik,

I took a look in the log file you provided and figured out the reason why your SASUnit run did not succeed. The main reason is SASUnit could not figure out the modification date of your test scenarios. Apparently aout using a german install of windows right? We're using a windows command shell and a dir command to retrieve the modififcation date of all test scenarios.
Obviously you are using the following date format: yyyy-mm-dd.
Time format hh:mm without AM/PM.
Now there are two ways to get SASUnit running.

1. Change your date format to dd-mm-yyyy as SASUnit expects for a german WINDOWS installation.
2. Change date format in _dir.sas in the windows folder.Therefore you need to change the highlighted row in the macro see attachment. The if block starts at row 107. In row 109 the date string is coverted to as SAS date value. the new format should be yymmdd10.

We need to get rid of date formating problems. I will create a new ticket therefore.

Regards
Klaus Landwich