toEqual output is truncated

[PupoSDC]

Describe the bug

This is a follow up to #2448 Since I simply don't understand the solution being proposed.

When running a test to check the equality of two objects, the output is truncated if there are more than 2 properties.

I.e. the output looks like this:

AssertionError: expected { hello: 'world', …(3) } to deeply equal { hello: 'world', …(2) }

Which means it's not possible to establish what was wrong.

I wondered if setting this might help but it doesn't seem to make a difference here.

Here is the output i see on my console:

Here is the output from Jest, which is more or less what I was expecting to see:

How can i make it so that the full diff between the provided and expected value is shown on the console?

Reproduction

In this repo there's a test called it demonstrates toEqual output is truncated in ApiCaller.test.ts that shows the problem.

System Info

System:
    OS: macOS 13.4
    CPU: (8) arm64 Apple M1 Pro
    Memory: 3.56 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.1 - ~/Library/Caches/fnm_multishells/54988_1688995060872/bin/node
    Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/54988_1688995060872/bin/yarn
    npm: 9.5.1 - ~/Library/Caches/fnm_multishells/54988_1688995060872/bin/npm
  Browsers:
    Chrome: 114.0.5735.198
    Safari: 16.5

Used Package Manager

yarn

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sheremet-va]

Linked reproduction prints the output

[github-actions]

Hello @PupoSDC. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[PupoSDC]

Thank you for your reply. Our setup was missing the following config on vite.config.js:

export default defineConfig(() => {
  return test {
      outputTruncateLength: 10000,
      outputDiffLines: 100000,
  }
}

It appears that by default no diff is generated.

Thank you!

[sheremet-va]

Thank you for your reply. Our setup was missing the following config on vite.config.js:

export default defineConfig(() => {
  return test {
      outputTruncateLength: 10000,
      outputDiffLines: 100000,
  }
}

It appears that by default no diff is generated.

Thank you!

Both of these options are not supported by Vitest for some time now.

[PupoSDC]

So what Options should I set? These 2 seem to work on vitest: 0.33.0.

Which is supposed to be the correct set of options for this version?
And where can i find the docs for them?

[sheremet-va]

So what Options should I set? These 2 seem to work on vitest: 0.33.0.

Which is supposed to be the correct set of options for this version? And where can i find the docs for them?

There are no options for diff. It should just work, and it works without any options in linked reproduction.

[Mouvedia]

[PupoSDC]

@Mouvedia Check if you are running the latest vite (0.33 at this date) that was the issue for me.
On this version the settings flag outputTruncateLength, outputDiffLines are indeed not needed.

[Mouvedia]

I am using version 0.33.0.