qunitjs / qunitjs/qunit

Implicit and naive cloning of comparable objects causes errors

Open
#1,782 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: Assert Type: Bug
Dominant language
JavaScript
Stars
4k
Forks
773
PR merge metrics
No merged PRs in 30d

Description

const object = { get x() { throw 42 }};
assert.equal(object, object); // => Died on test qunitjs/node-qunit#1: 42

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.

Research direction

Start by reproducing the JavaScript snippet in the QUnit assertion tests and trace how assert.equal compares objects with getters. Determine the intended behavior for a comparable object whose getter throws, then add a regression test showing that behavior and run the relevant assertion tests.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.