You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I been using deno test in the simple describe > it fashion, and it's alright. The only downside I've encounter is when multiple test's are failing, it gets cluttered real quickly with long stack traces. When writing good describe-it combinations I already now where and what failed, so it's not necessary that whole stack trace. Adding -q flag won't help it.
Current:
describe it description yara yara
error: AssertionError: Values are not equal.
[Diff] Actual / Expected- undefined
+ "poussar" <-- up to here would be okay some times :)
throw new AssertionError(message);
^
at assertEquals (https://deno.land/std@0.203.0/assert/assert_equals.ts:53:9)
at Object.<anonymous> (file:///media/martincito/freedom/repos/grammy/commands/test/jaroWrinkler.test.ts:169:21)
at Function.runTest (https://deno.land/std@0.203.0/testing/_test_suite.ts:358:16)
at Function.runTest (https://deno.land/std@0.203.0/testing/_test_suite.ts:346:33)
at Function.runTest (https://deno.land/std@0.203.0/testing/_test_suite.ts:346:33)
at Function.runTest (https://deno.land/std@0.203.0/testing/_test_suite.ts:346:33)
at Function.runTest (https://deno.land/std@0.203.0/testing/_test_suite.ts:346:33)
at fn (https://deno.land/std@0.203.0/testing/_test_suite.ts:316:37)
#13586 and #14921 mention shortening the stack trace. I would like a flag to completely remove it.
Desired:
describe it description yara yara
error: AssertionError: Values are not equal.
[Diff] Actual / Expected- undefined
+ "poussar"
Call it --hide-traces or --hide-stack-trace or whatever you wanna call it, but as of rn its too much visual noise. Thanks
The text was updated successfully, but these errors were encountered:
I been using deno test in the simple
describe
>it
fashion, and it's alright. The only downside I've encounter is when multiple test's are failing, it gets cluttered real quickly with long stack traces. When writing good describe-it combinations I already now where and what failed, so it's not necessary that whole stack trace. Adding -q flag won't help it.Current:
#13586 and #14921 mention shortening the stack trace. I would like a flag to completely remove it.
Desired:
Call it --hide-traces or --hide-stack-trace or whatever you wanna call it, but as of rn its too much visual noise. Thanks
The text was updated successfully, but these errors were encountered: