Using in a Unit Testing environment

[davestewart]

Not sure if this is the right place to ask, but when attempting to use in Jest tests, I get the following error:

This script should only be loaded in a browser extension

I was attempting to use in conjunction with sinon-chrome to mock the Browser API and begin to test my extension, but I can't seem to get the chrome object in the right context for the polyfill to work:

acvetkov/sinon-chrome#103

I'm a "fair weather" tester, so I will be the first to admit I may have no idea what I'm doing and perhaps should not be tackling things this way.

Can anyone advise?

Thank you.

[nickserv]

This fixed it for me #218 (comment)

[Rob--W]

Duplicate of #218. Thanks nick for linking #218 (comment)

[davestewart]

Thanks @nickmccurdy and @Rob--W!

Not sure why I didn't search the issues.

Not sure if you consider it in-scope to perhaps add a section (even links) to the home page?

It's really the next logical step for anything you expect to be used my more than a few people.

Thanks again 👍

[Rob--W]

I think that the best way to solve this bug is to set a non-void extension ID in chrome.runtime.id in the sinon-chrome library (or at least document it there). This "problem" is not specific to this polyfill, but generally to any consumer of sinon-chrome.

[nickserv]

Should we suggest a fix upstream? It seems like a common issue, I'm not sure why it's initialized to null.

[Rob--W]

It wouldn't hurt to ask. sinon-chrome's primary responsibility seems to be the generation of stubs, and it's up to the consumers of that library to provide meaningful implementations. In this case, a value for chrome.runtime.id.