QUnit's noglobals setting catches __SENTRY__

[amk221]

I like to use QUnit's noglobals setting. (and I don't particularly want to disable it)

After upgrading Sentry, some of my tests are failing due to the introducion of a __SENTRY__ global.

There doesn't appear to be a way in QUnit to specify globals to ignore.

Any ideas of the best course of action?

[AbhiPrasad]

Can you just not enable Sentry/use Sentry methods in test environments? That should make sure no Sentry global is added.

[amk221]

Hi, so Sentry is already disabled in the test environment. As in, Sentry.init is not called.

But the app code may still do something like Sentry.captureMessage(...)

I don't want to have to wrap that in an if (inProd) { for example...

🤔

[AbhiPrasad]

Yeah I agree that is not ideal, but we have to use rely on the global for our Sentry APIs.

Is there a workaround by adding the __SENTRY__ global before the test starts?

[amk221]

Yeh that'll do it, thanks

I am little bit curious how __SENTRY__ has become needed, since it wasn't previously.