I have added proper jsdoc. And it looks like that is all I need to do to update the documentation. For that reason, I am going to check that box in the PR checklist above.

How do I access the spy on the spied property?

It would be something like this:

let obj = { a: () => true };
spyOnAll(obj);
obj.a();
expect(obj.a).toHaveBeenCalled();

Or maybe I'm misunderstanding your question.

That’s for a function. How about for a property? If ‘a’ is a property, how do we differentiate between getting the property value vs. the spy?

That's a good question. I have never used spies on non-functions before. Perhaps I should restrict spyOnAll to functions only. (and perhaps rename to spyOnAllFunctions)

And then there could be an equivalent spyOnAllProperties to be implemented at a later date.

I haven’t had a chance to review this in any more detail, but let’s either update the name or add the property spying (or both so there is spyOnAll, spyOnAllFunctions, and spyOnAllProperties or something)

Updated the commit so that it provides spyOnAllFunctions. Do you want me to update the PR text as well? If and when this goes through, I'll add spyOnAllProperties.

I don't know a lot about developing in this repo, but I noticed that I cannot use spyOnAllFunctions without first constructing a registry. Was that intended behavior? Currently,

it("does a thing", function() {
    spyOnAllFunctions(someThingToSpyOn);
});

throws env.spyOnAllFunctions is not a function.

Adding the following to Env.js seems to fix my problem.

this.spyOnAllFunctions = {
  return spyRegistry.spyOnAllFunctions.apply(spyRegistry, arguments);
}

You're right, it looks like a bit of the wiring got missed for this. I'm releasing a 3.2.1 which should work properly out of the box.

+1 !

Took me a long time to find this PR, excited for this.

Unfortunately, I am not currently on the latest version, but very glad with the addition.

is there a way to use this with classes instead of objects?