---
- branch: MAIN
  date: Tue Feb 14 15:08:42 UTC 2023
  files:
  - new: '1.2'
    old: '1.1'
    path: pkgsrc/devel/shunit2/Makefile
    pathrev: pkgsrc/devel/shunit2/Makefile@1.2
    type: modified
  - new: '1.4'
    old: '1.3'
    path: pkgsrc/devel/shunit2/distinfo
    pathrev: pkgsrc/devel/shunit2/distinfo@1.4
    type: modified
  id: 20230214T150842Z.c419ca3699d7324b0065a6b79eceaabda7c663bb
  log: |
    Update to 2.1.8. From the changelog:

    # New features

    Users can now define a custom prefix for test function names. The prefix
    can be configured by defining a `SHUNIT_TEST_PREFIX` variable.

    Colorized output, based on popular demand. shUnit2 output is now
    colorized based on the result of the asserts.

    # Changes and Enhancements

    Shell commands in shUnit2 are prefixed with '\' so that they can be
    stubbed in tests.

    # Bug fixes

    Syntax errors in functions are now treated as test failures.

    Test now fail when `setup()` or `tearDown()` fail.

    shUnit2 no longer exits with an 'OK' result if there were syntax errors
    due to incorrect usage of the assert commands.

    # Known bugs and issues

    Zsh requires the `shwordsplit` option to be set. See the documentation
    for examples of how to do this.

    Line numbers in assert messages do not work properly with BASH 2.x.

    The Bourne shell of Solaris, BASH 2.x, and Zsh 3.0.x do not properly
    catch the SIGTERM signal. As such, shell interpreter failures due to
    such things as unbound variables cannot be caught. (See
    `shunit_test_misc.sh`)

    shUnit2 does not work when the `-e` shell option is set (typically done
    with `set -e`).

    # Tested platforms

    Tested OSes:

    - Linux
    - macOS

    Tested shells:

    - /bin/sh
    - ash
    - bash
    - dash
    - ksh
    - pdksh
    - zsh
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/shunit2'
  unixtime: '1676387322'
  user: schmonz