What's new in SASUnit 1.2
Mar 4, 2013
- Enhancements:
- This is the first release of SASUnit where project management has been fully hosted on SourceForge, so this is a starting point for faster release cycles and for better integration of the HMS development team and the user community in the future.
- Support for different environments has been reorganized, there now is a pair of command files for each scenario, one for complete execution of the test suite and one for incremental execution of changed programs only.
- Projects can now be moved without the need to change command files.
- Command files now pause when there is an error or a warning.
- Testing procedures have been improved by the means of more unit tests and a detailed test plan, also across different environments.
- The main page now includes more information about the execution environment (SAS version, configuration, user id etc.).
- The SASUnit logo has been changed to the green OK symbol and it now links to SourceForge.
- There is a new assertion for performance tests (assertperformance.sas).
- Example regression_test.sas has been enhanced for better comprehensibility (see regression.xls) and is now also available under SAS on Linux.
- Added support for testcases that need to redirect logfiles. Macro variables g_logfile and g_printfile hold the redirected paths used by SASUnit.
- Solved defects:
- Errors resulting from special characters in parameters of SASUnit macros have been fixed.
- Missing style sheet in assertreport has been added.
- Errors in the scenario log are now being highlighted in the scenario details report.
- Scenarios without a valid test case are reported as well.
- Missing test scenario programs are reported as well.
- Problems with English settings of Microsoft Windows have been solved.
- Column "number of test cases" on overview page for units under test wrongly showed number of checks, this has been fixed and column "number of checks" has been added.
- Warning and error messages have been eliminated from run_all.log.
- Fixed issue where %sysexec call to SAS for running of test scenarios failed because the call string became too long.
- Some additional minor bugs have been solved.