Open SamuelMelm opened 1 year ago
Should already be implemented, see parameter i_autoexec.
Originally created on SourceForge by amangold - 16.07.2012, 11:37
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.
Originally created on SourceForge by j-lang - 17.07.2012, 13:02
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?
Originally created on SourceForge by amangold - 17.07.2012, 21:27
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. Does this clarify my scenario?
Originally created on SourceForge by j-lang - 18.07.2012, 07:05
OK, accepted. We will decide on that later.
Originally created on SourceForge by amangold - 18.07.2012, 07:46
Integrate a project specific autoexec.sas program in order to use SASUnit in existing projects. (Johannes Lang)
Originally created on SourceForge by amangold - 16.07.2012, 11:35