That's true. But it can (and perhaps should) be clarified how to reference a project-specific autoexec.sas even at SASUnit startup, e.g. when paths, macrovariables shall be defined there and not in the start script itself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What do you mean by at "SASUnit startup"? The program specified for parameter i_autoexec will be executed at the start of every test scenario because a new SAS session is being started for every scenario. Do you want an initialization for every test case?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I mean, when I launch SASUnit by executing the OS-specific start script.
Then I want to run my autoexec before SASUnit runs run_all.sas, so that I can use my global macro variables in run_all.sas. For example, I defined the path where SASUnit itself resides on my disk in this autoexec.sas. Then I want to use this variable in run_all.sas, to avoid hardcoded environment info there. (BTW, there seems to be a ticket that addresses this matter -> [#7]). Does this clarify my scenario?
Should already be implemented, see parameter i_autoexec.
That's true. But it can (and perhaps should) be clarified how to reference a project-specific autoexec.sas even at SASUnit startup, e.g. when paths, macrovariables shall be defined there and not in the start script itself.
What do you mean by at "SASUnit startup"? The program specified for parameter i_autoexec will be executed at the start of every test scenario because a new SAS session is being started for every scenario. Do you want an initialization for every test case?
I mean, when I launch SASUnit by executing the OS-specific start script.
Then I want to run my autoexec before SASUnit runs run_all.sas, so that I can use my global macro variables in run_all.sas. For example, I defined the path where SASUnit itself resides on my disk in this autoexec.sas. Then I want to use this variable in run_all.sas, to avoid hardcoded environment info there. (BTW, there seems to be a ticket that addresses this matter -> [#7]). Does this clarify my scenario?
Related
Tickets:
#7OK, accepted. Maybe we should integrate that into [#7]. We will decide on that later.
Related
Tickets:
#7