Hi,
I am testing SASUnit framework, but I found only the part of generating html report has been implemented in code even there is one parameter for generating PDF there, am I right? Since there are so many subroutine macros involved, it is hard for me to read through the code and modify it, so I am wondering there are any updating of code for PDF reports.
I submit my code to remote UNIX server, so there is no way to view html for me. Thanks
Eric
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
there are some implementations done for creating a single PDF-Report document.
The status of PDF-reproting is experimental, because we are not quite sure what would be needed in a PDF-Report and what should be left out.
Will there only be one PDF-Document or numerous one's?
Since there was no need so far to have an running PDF-Documentation we didn't spent much time on this issue.
I attached the current PDF-Report for the example project.
The PDF-Document will be saved in the same location (for you on the remote UNIX server) as the HTML-Reports.
There is one reporting macro, that opens and closed all ods destinations: reportsasunit.sas.
Another macros creates documentations for each macro: _pgmdoc.sas.
Any other rendering is done in corresponding rendering macros per html page (_reporthomehtml etc) or assertion type (_render_<assertType>act or _render_<assertType>exp).
That's the way it is.
What is the problem with the HTML-Files. Can't you open them because you have no browser under UNIX? Could you open PDF instead, but not HTML?
Please specify further so we can give you an suitable solution.
Thanks Klaus for the reply and sample. I hope there is only one PDF report. The problem with HTML files is that we sumbit our code to run at remote UNIX server via our EG, so we can't view the generated HTML files directly.
My impression/suggestion to improve is:
1. Third party software doxgen limit it's use. We have no way to install doxgen on the remote server because we are not the owner of the server.
2. There is no step by step tuturial for this framwork for UNIX environment. It is daunting for the beginers or even some experienced programmers to integrate the framework into their system
But thank you anyway for this pioneering work in SAS testing. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Support Requests" comments posted by this user
Mark all as spam, and block user from posting to "Forum"
Hi,
I am testing SASUnit framework, but I found only the part of generating html report has been implemented in code even there is one parameter for generating PDF there, am I right? Since there are so many subroutine macros involved, it is hard for me to read through the code and modify it, so I am wondering there are any updating of code for PDF reports.
I submit my code to remote UNIX server, so there is no way to view html for me. Thanks
Eric
Hi Eric,
there are some implementations done for creating a single PDF-Report document.
The status of PDF-reproting is experimental, because we are not quite sure what would be needed in a PDF-Report and what should be left out.
Will there only be one PDF-Document or numerous one's?
Since there was no need so far to have an running PDF-Documentation we didn't spent much time on this issue.
I attached the current PDF-Report for the example project.
The PDF-Document will be saved in the same location (for you on the remote UNIX server) as the HTML-Reports.
There is one reporting macro, that opens and closed all ods destinations: reportsasunit.sas.
Another macros creates documentations for each macro: _pgmdoc.sas.
Any other rendering is done in corresponding rendering macros per html page (_reporthomehtml etc) or assertion type (_render_<assertType>act or _render_<assertType>exp).
That's the way it is.
What is the problem with the HTML-Files. Can't you open them because you have no browser under UNIX? Could you open PDF instead, but not HTML?
Please specify further so we can give you an suitable solution.
Last edit: Klaus Landwich 2017-01-16
View and moderate all "Support Requests" comments posted by this user
Mark all as spam, and block user from posting to "Forum"
Thanks Klaus for the reply and sample. I hope there is only one PDF report. The problem with HTML files is that we sumbit our code to run at remote UNIX server via our EG, so we can't view the generated HTML files directly.
My impression/suggestion to improve is:
1. Third party software doxgen limit it's use. We have no way to install doxgen on the remote server because we are not the owner of the server.
2. There is no step by step tuturial for this framwork for UNIX environment. It is daunting for the beginers or even some experienced programmers to integrate the framework into their system
But thank you anyway for this pioneering work in SAS testing. :)