`td.imitate` produces `undefined` for object keys of type `Accessor`

[italodirenzo93]

Description

I'm working on a Next.js app that uses testdouble.js for mocking dependencies in tests. Our test environment uses Jest and runs under Babel. This issue revealed itself when attempting to alter our Jest config to use the Next.js Compiler (SWC) as described here.

The following code snippet run under Babel results in a passing test.

const myDependency = td.replace("../lib");

td.when(myDependency.doTheThing()).thenReturn(123);

expect(myFunction()).toBe("some result");

The same test run under SWC fails with the error

TypeError: myDependency.doTheThing() is not a function

Issue

Objects with Accessor properties result in undefined when run through td.imitate.

For example, given:

class Foo {
  get bar() {
    return 0;
  }

  baz() {
    return 1;
  }
}

The line:

const instance = new Foo();

produces an object with the type

{ bar: Accessor, baz: Function }

Running the class instance through td.imitate

const imitation = td.imitate(instance);

results in an object with the type

{ bar: undefined, baz: Function }

Environment

• node -v output:
• npm -v (or yarn --version) output:
• npm ls testdouble (or yarn list testdouble) version:

Failing Test

• Fork the repo
• Add a failing test (probably to the `/regression/src' directory)
• Submit a pull request for the failing test or link to your branch here

Example Repo

• Create a minimal repository that reproduces the issue
• Make sure that a fresh clone can run only npm it and observe the issue
• Link to that repo here

Runkit Notebook

• Create a Runkit notebook
• Invoke var td = require('testdouble') at the top
• Verify the behavior your issue is concerned with by clicking "Run"
• Link to the Runkit here