assert.Equal shows diff that does not affect success of test

Open
#635 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the assert.Equal example with pointer values that compare equal but have different addresses, then inspect the diff output path used by assert.Equal. Done means the failure diff no longer highlights pointer addresses that do not affect equality, while meaningful differences remain visible.

Written by the indexing model from the issue text.

Description

For instance:

			-    Position: (*int64)(0xc4200a3348)(1),
			+    Position: (*int64)(0xc4200be780)(1),

But that values are not a reason fail of test.

Do we need this behavior?
I got some confused with that, I could try to change it.

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.