Difference between "deno test" and "VSCode Runner UI"
Hello.
When using the
deno test
command I'm getting some failures (What is not expected).
But when I use the VS Code interface and I press play button next to the deno test. Everythig passes like expected1 Reply
Hello!
I wasn't able to find the answer to your question in the official Deno documentation. However, based on the information you've provided, it seems like there might be a discrepancy between the environment or configuration when running tests through the
deno test
command and the VSCode Deno Test Runner UI.
One possible reason for this discrepancy could be differences in environment variables, Deno permissions, or other settings that are applied differently when running tests from the command line versus the integrated test runner in VSCode.
Please note that this advice is not based on the Deno documentation, and I would advise you to double-check the accuracy of this advice. It might be helpful to ensure that the same permissions and environment variables are used in both cases. Additionally, consider checking if there are any settings within VSCode that might be influencing the test outcomes.
If the issue persists, you may want to look into the specific tests that are failing when using the deno test
command and see if there's any code that could be dependent on the environment or configuration that differs from what the VSCode extension uses.