lowlight
Deno.test without Deno namespace ?
Yeah finally I went with just not testing other environments in Deno. It makes more sense like you said and seems more clean indeed. It just that the ocd was triggered by the red lines shown in deno coverage
Just to clarify, the workers weren't really part of the code, it was just a workaround for creating a "Realm" since ShadowRealms are not yet supported. Removing deno namespace from them was mostly to "simulate" a browser environment.
Thanks for taking the time to answer and for your thoughtful explanation
9 replies
Deno.test without Deno namespace ?
I got this part right, but my question was more oriented towards testing and coverage
Like in your example, how would you use
Deno.test
to pass into the "non-deno" branch ?
I'd like to avoid using something this (unless it's the only way):
Currently I use something like this so it doesn't affect the global env as workers are kind of sepearate thread, but because of the bug mentionned, the code executed within workers is not covered
9 replies