Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

osal Integration candidate: 2021-08-24 #1132

Merged
merged 3 commits into from
Aug 21, 2021
Merged

Commits on Aug 18, 2021

  1. Fix #1130, add test case types similar to NA

    Add two more test case variants, similar to NA, where failure
    of the test case does not translate to failure of the overall
    test:
    
     - UTASSERT_CASETYPE_WARN
     - UTASSERT_CASETYPE_FLOW
    
    The additional cases have different levels of default visibility,
    and may be handled differently by the end user.  That is, some
    tests may be skipped because they are truly NA (and nothing for
    the user to do to change that) and some tests may be skipped
    because the system was not set up in a way that allowed them
    to be run (and the user must fix that and re-run).  For the
    latter case, the WARN type can be used, to more clearly
    indicate it is an action item for the user.
    
    Lastly the "FLOW" message is intended to indicate internal decisions
    in the test case implementation (not actual test cases).
    jphickey committed Aug 18, 2021
    Configuration menu
    Copy the full SHA
    70bb29b View commit details
    Browse the repository at this point in the history

Commits on Aug 19, 2021

  1. Merge pull request #1131 from jphickey/fix-1130-utassert-na-cases

    Fix #1130, add test case types similar to NA
    astrogeco authored Aug 19, 2021
    Configuration menu
    Copy the full SHA
    5d8eea4 View commit details
    Browse the repository at this point in the history

Commits on Aug 20, 2021

  1. Configuration menu
    Copy the full SHA
    640e1fd View commit details
    Browse the repository at this point in the history