Expose "require" suite

Open
#829 30 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
testing

Research direction

Start by reading the context in testify issue 599 and the existing suite.Suite and require.Assertions entry points. Define what a RequireSuite should expose while preserving normal suite behavior, then verify that its suite methods use require-style failures by default.

Written by the indexing model from the issue text.

Description

Breaking Change enhancement: extend API

I and many others expect / would prefer for the default behavior of the suite.Suite's .Equals() et al. methods to use the require behavior. See https://github.com/stretchr/testify/issues/599 for some context.

It would be nice if suite exposed a suite.RequireSuite, which could use the require.Assertions by default.

I left a comment in 599 outlining this struct. I believe that it should work just like the normal suite otherwise.

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.