Skip to content

Add expectation testing for available content types #1533

Open
@ehelms

Description

Just thinking out loud (because I thought about a similar case in the past just for smoker): you can have an env var (like EXPECT_OSTREE) where missing means auto-detection, YES means failure if it isn't present and NO means failure if it is present.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions