Mocks, would they always be the same?

Open
#647 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files, tests, or entry points and asks a general design question about exporting mocks with Go interfaces. Clarify whether a concrete repository change is wanted, then define the expected mock ownership and any acceptance criteria before selecting implementation or tests.

Written by the indexing model from the issue text.

Description

Hey,

A more general question on mocks.

Say, i implement a library (provider) that has certain interfaces exported. On consumer side i put some tests, where i need interfaces mocked. As it goes i see mocked methods will be almost always exactly the same (is not about particular mock implementation but to ilustrate the question):

func (m *MockedInterface)  MockedFunction(argument string) error{
     args:=m.Called(argument)
     if args.Error(0)!=nil{
          return args.Error(0)
     }
     return nil
}

Therefore does it make sense to export mock together with the interface, or should mock be declared and implemented on consumer side? Whats the best way of doing and why...

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.