--- old+++ new@@ -4,3 +4,5 @@sasunit.9.2.linux.en.sh
sasunit.9.2.linux.en.overwrite.sh
sasunit.9.2.linux.en.cfg
++Testing environment should be as close to the existing windows testing environment [#68] als possible.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
According to today's status meeting, there are now two Linux machines, one with UBUNTU and one with SUSE.
Tasks: Together with KL, choose one machine, document choice here, and establish complete testing environment on that machine, similar to windows machine. Write documentation about the machine and the SASUnit implementation there. After that, porting to the other machine could be done.
Last edit: Andreas Mangold 2012-10-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Testing environment has been established on Suse with SAS 9.2 English. Since Nikolas currently cannot commit, scripts and necessary enhancements are not yet in the repository.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please run example project and all self tests on Ubuntu SAS 9.3, report any errors to colleagues.
Provide Ubuntu SAS 9.3 on VMware server (->IT Service)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When starting cmd scripts from a GUI shell, possible errors should become visible. Under windows, this has been accomplished by the way of conditional pause statements. A similar solution should be implemented for the various Linux scripts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
--- old+++ new@@ -1,8 +1 @@-see Reorganize support for different environments [bugs:#7]--shell command files and config files should be named as follows:-sasunit.9.2.linux.en.sh-sasunit.9.2.linux.en.overwrite.sh-sasunit.9.2.linux.en.cfg--Testing environment should be as close to the existing windows testing environment [#68] als possible. +Two test VMs for SASUnit (linux-amws and ubuntu-sasunit) created/configured and in HMS wiki documented
status: assigned --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
--- old+++ new@@ -1 +1,8 @@-Two test VMs for SASUnit (linux-amws and ubuntu-sasunit) created/configured and in HMS wiki documented+-see Reorganize support for different environments [bugs:#7]+-+-shell command files and config files should be named as follows:+-sasunit.9.2.linux.en.sh+-sasunit.9.2.linux.en.overwrite.sh+-sasunit.9.2.linux.en.cfg+-+-Testing environment should be as close to the existing windows testing environment [#68] as possible.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
--- old+++ new@@ -1,8 +1,6 @@--see Reorganize support for different environments [bugs:#7]----shell command files and config files should be named as follows:--sasunit.9.2.linux.en.sh--sasunit.9.2.linux.en.overwrite.sh--sasunit.9.2.linux.en.cfg----Testing environment should be as close to the existing windows testing environment [#68] as possible.+* Reorganize support for different environments [bugs:#7]+* shell command files and config files should be named as follows:+ * sasunit.9.2.linux.en.sh+ * sasunit.9.2.linux.en.overwrite.sh+ * sasunit.9.2.linux.en.cfg+* Testing environment should be as close to the existing windows testing environment [#68] as possible.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ticket_type: Defect_Report --> Task_Assignment
Description has changed:
Diff:
According to today's status meeting, there are now two Linux machines, one with UBUNTU and one with SUSE.
Tasks: Together with KL, choose one machine, document choice here, and establish complete testing environment on that machine, similar to windows machine. Write documentation about the machine and the SASUnit implementation there. After that, porting to the other machine could be done.
Last edit: Andreas Mangold 2012-10-10
Testing environment has been established on Suse with SAS 9.2 English. Since Nikolas currently cannot commit, scripts and necessary enhancements are not yet in the repository.
Please run example project and all self tests, report any errors to colleagues.
Please run example project and all self tests on Ubuntu SAS 9.3, report any errors to colleagues.
Provide Ubuntu SAS 9.3 on VMware server (->IT Service)
added support for SAS 9.3 for linux ; test with Ubuntu VM successful
When starting cmd scripts from a GUI shell, possible errors should become visible. Under windows, this has been accomplished by the way of conditional pause statements. A similar solution should be implemented for the various Linux scripts.
Add tests for the cases where autoexec and/or config files of test scenario environments are different from the calling process.
Diff:
Diff:
Diff:
There are now 2 linux test VMs: