Skip to content

API approval tests #1133

@jnyrup

Description

@jnyrup

Description

In order to help not breaking semantic versioning, we should include API approval tests to verify that any changes to the public API of each targeting framework are explicitly verified.

FakeItEasy does this quite neatly using PublicApiGenerator.
See https://github.com/FakeItEasy/FakeItEasy/tree/master/tests/FakeItEasy.Tests.Approval

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions