SASUnit Version 2.1

Changes since version 2.0.2

Major Changes

• Discontinuity of SAS9.3
  • Due to SAS and Microsoft strategy the only SAS version supported under Windows 10 ist SAS 9.4. In conequence we needed to cut off support for SAS 9.3 under Windows
  • For Linux environments we switched to CentOS and decided for simplicity of maintenance to cut off SAS 9.3 too.
  • You will still be able to run SASUnit with SAS 9.3 on both platforms, but we will focus on SAS 9.4 for development and testing.
• SASUnit now provides a setup script
  • To simplify the setup process of SASUnit there is an setup script available.
  • It's the only file you need to adjust with your personal environment. It will then created multiple start scripts for SASUnit with your personal project.

New Features

• SASunit uses log4sas specified in a logconfig.xml
  • Now it is possible to use SASUnit in projects that also use an logconfig.xml
  • Messaging was completely change to log4sas
  • There are numerous log files
    • the traditional run_all.log
    • a new aggregated log file for the test suite
    • a new aggregated log file for all scenarios
    • a new log file containing all assert and the result. It has the same content that is written to the test data base. So this can be a prototype for running SASUnit without test data base.
• Paths within SASUnit have "/" as separator and are not quoted. No double quotes around paths with blanks for Windows nor a "\ " under Linux.
  • This facilitates implementing SASUnit features. Only when communicating with the operating system the paths will be adjusted.
• Support standard linux paths
  • Under Linux SASUnit can now be splitted across etc, opt, var "as usual".
• Tidy up HTML folder
  • HTML folder now has subfolders to restrict the number of files in the root folder of the documentation
• User contribution by Chuck Castillo
  • New coveniance assertion assertTrue
• Assert as place holder for manual Tasks
  • New assertion assertManual
• New layout of target.tsu
  • For each new parameter we use in SASUnit we had to change the layout (e.g. variables) of this table.
  • The table is now implemented as a key-value-pair for each paramter
  • Introducing new parameters will not change the layout anymore.

Enhancements

• assertRecordCount
  • assertRecordCount now always shows the counted observatios. This is espacially usefull when working with a where expression.

Solved defects

• assertLogMsg
  • assertLogMsg converted the passed string to uppercase to eliminate case sensitivity. If there are regEx modifiers in string they where also converted to uppercase, which may result in a different meaning.
  • Therfore a new parameter was introduced for case sensitivity. The uppercase conversion was replaced be adding "/i" to the regEx string.

Other changes

• Test coverage of SASUnit self tests
  • For each macro there is at least an "empty" test scenario resulting in statement coverage.
  • This will guide future creation of additional self tests
• Conveniance change for test cases that will run on both platforms
  • For assertImage and assertText there are script files that are dependent on the operating system.
  • To run these asserts on platforms alike an independent scenario was created to cover simple functionality of the script files.

Contributors

Klaus Landwich (project management, development)
Chuck Castillo (develoment assertTrue)
Anne Kirchmann (documentation)
Dr. Patrick Rene Warnat (development test coverage)
Johannes Lang (development)
Nikolas Aggelidakis (Linux development)
Bernhard Braun (testing and develoment)
Leonhard Rohr (develoment)
Oliver Thieleman (develoment)
Grischa Pfister (project management)
Roland Mannshardt (project management)
Andreas Mangold (project management)