Klaus Landwich

Hi Henrik, I'm not 100% sure where this comes from but this is my first guess. Image comparison cannot be done with in SAS so we need a third party tool to conduct that job. It is called imageMagick. You need to install that on the machine where SASUnit is running. Currently SASunit support the command line interface of version 6.9.13 Including imageMagick into SASUnit at first was only to show what you can do with assertExternal. But then it came in quite handy. If you cannot install that to your...

Hi Henrik, We are currently working on version 2.2 of SASUnit. This includes some bug fixes and a bit refactoring. In parallel we are evaluating how SASUnit can be integrated into SAS Viya architecture. We plan to update SASUnit batch processing to be able to start "SAS Sessions" under SAS Viya. Regards Klaus

Hi Henrik, yes, it is possible to "test" python code with SASUnit. You can start the call to python as your test call in SASUnit. I'm not sure what portion of the python log / output will be visible in the SAS log file. That surely depends on the way you call the python program. You can then check the results (e.g. report or data set) with SASUnit. %initScenario(i_desc=Tests for python program xyz); %initTestcase(i_object=call_python_program_xyz.sas, i_desc=Call with Parameters abc) <...call python...

Hello Henrik Lissau, your previous e-mail did reach me. I justed hadn't the time to react yet. From a validation point of view SASUnit is not part of your source code. So you do not need to validate it. As for any third-party tool you need an installational and operational qualification. This can be done by executing the sample project we deliver with SASUnit and compare it to the documentation on SourceForge or GitHub. In case you need some documentation or are interested in our testing of SASUnit...

different location for sasunit installation and SAS programms

This is a reasonable approach. As we created the setup script we didn't have that in mind. SASUnit currently is capable to do so, but not the setup routine. To minimze manual editing of script files you can do the following: 1. Temoprarily created copy run_all.sas into ....\sasunit_prj\saspgm 2. Configure setup script to have ...\sasunit_prj as SASUNIT_PROJECTFOLDER 3. Start setup script 4. Remove run_all and saspgm folder 5. Update your run_all.sas to use absolute path to autocall members 6. Update...

Getting-Started-Video for SAS EG integration

Live on Youtube