Make possible override assertion implementation

Open
#795 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
testing-qa

Research direction

Start by reviewing the assertion implementation and how the default Assertions type is exposed. Determine how an override such as require.Assertions would be configured without changing existing behavior. Done means the implementation can be overridden and the existing assertion APIs remain compatible; the issue names no specific files or tests.

Written by the indexing model from the issue text.

Description

For example:

  • make it as require.Assertions instead of default Assertions.

I guess I can implement it if you ok with that idea.

Dominant language
Go
Stars
26.2k
Forks
1.9k
Avg merge
2d 4h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stretchr/testify

All issues in stretchr/testify

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.