#7 Reorganize support for different environments

[Andreas Mangold]

What is an environment?

SASUnit depends on its environment: the OS, its version and language settings and on the SAS version and its configuration. One specific combination of those environmental factors constitutes one environment. Up to now, the control environment (SAS session which selects the scenarios to be run, spawns SAS sessions for execution of scenarios and generates reports) and the execution environment (SAS sessions which execute the test scenarios) are always the same, besides from being able to use a specific SAS configuration file for the execution environment (parameter i_sascfg in initsasunit.sas).

What has to be reorgnized?

The following things should be done in order to facilitate usage of SASUnit in different environments:

Identify and document target environments

We have to identify the target environments in order to clearly state for which environments SASUnit has been designed and tested. Usage and special considerations for each target environment have to be documented in the user documentation. The field "Environement" in the ticket system has to be updated in order to show all the identified environments. Other environments can always be used, but will not be tested as thoroughly.

Tidy up configuration and batch files

The configuration files and the batch programs can be found in the bin and example/bin folders. They have to be consistently named according to the target environments.

Pass paths from batch files

It should not be necessary to change run_all.sas in order to provide the correct paths, at least in standard situations. Paths could be passed from the batchfiles, so only they need to be changed.

Provide pairs of batch files for run all and for run only changed

SASUnit cmd files for every environment should be duplicated, one to run all scenarios and one to run only the ones where the scenario itself or the unit under test have been changed since the last run. It should be considered whether additional batch files for report generation should also be provided.

[Andreas Mangold]

We have decided to support the following two environments:

Windows 7 64 bit SAS 9.3 64 bit (so we have no problems with Excel), OS German, SAS German (later English/English)

Linux (Ubuntu, Redhat Enterprise - to be decided), SAS 9.2, OS English, SAS English

Implementation see:
Provide testing environment for SAS 9.3 under Windows [bugs:#68]
Reorganize CMD scripts for Windows [bugs:#72]
Find out Linux version for testing [bugs:#69]
Provide testing environment for SAS 9.2 under Linux [bugs:#74]

[Andreas Mangold]

task [#83] Setup english windows testing environment

[Klaus Landwich]

• Description has changed:

Diff:

--- old
+++ new
@@ -1,6 +1,6 @@
 ###What is an environment?###
 SASUnit depends on its environment: the OS, its version and language settings and on the SAS version and its configuration. One specific combination of those environmental factors constitutes one environment. Up to now, the control environment (SAS session which selects the scenarios to be run, spawns SAS sessions for execution of scenarios and generates reports) and the execution environment (SAS sessions which execute the test scenarios) are always the same, besides from being able to use a specific SAS configuration file for the execution environment (parameter i_sascfg in initsasunit.sas). 
-###What has to reorgnized?###
+###What has to be reorgnized?###
 The following things should be done in order to facilitate usage of SASUnit in different environments:
 ####Identify and document target environments####
 We have to identify the target environments in order to clearly state for which environments SASUnit has been designed and tested. Usage and special considerations for each target environment have to be documented in the user documentation. The field "Environement" in the ticket system has to be updated in order to show all the identified environments. Other environments can always be used, but will not be tested as thoroughly. 

• status: accepted --> closed

[Klaus Landwich]

All dependend tickets are closed. Information is noted down in SASUnit User's Guide.