Skip to content

All content tests should raise errors when path does not exists #2

@gioele

Description

@gioele

Content tests are supposed to test what is inside a file. It is not good to let '/foo/bar'.as_path.empty? return false, it should raise an error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions