Skip to content

Consider switching test assertions to alecthomas/assert #5447

Open
@Jacalz

Description

@Jacalz

Checklist

  • I have searched the issue tracker for open issues that relate to the same feature, before opening a new one.
  • This issue only relates to a single feature. I will open new issues for any other features.

Is your feature request related to a problem?

While being quite well maintained and widely used, the testify/assert package is a huge package with mostly APIs that are not type safe. The second downside is that there are so many different APIs that almost do the same thing while also being possible to use in bad or otherwise incorrect ways. This is to the point of there even being a specific linter for this: https://github.com/Antonboom/testifylint

All of this makes me think that we should consider switching to https://github.com/alecthomas/assert. It does not necessarily have as much momentum behind it but it has a much simpler API and is type safe.

Is it possible to construct a solution with the existing API?

Not relevant

Describe the solution you'd like to see.

We should consider switching to https://github.com/alecthomas/assert. I did so recently for https://github.com/Jacalz/rymdport and I am happy with the result.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttestingIssues related to tests and testing.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions