Fork me on GitHub
#pedestal
<
2018-03-01
>
souenzzo00:03:36

I'm already picking up from the stack. Just digging about a more "standard/clean" way to do 🙂 tkx

eraserhd17:03:55

Is there a way to filter pedestal exceptions when running tests? Mine are currently about 8000 lines long, I think.

ddeaguiar19:03:32

@eraserhd you’ll need to dynamically change the logging level during your test runs. You can even do it at a per-test level but you’ll need to write code for that either way

ddeaguiar19:03:20

I’ve typically done this through a with-log-level macro

eraserhd19:03:43

This is for the exceptions shown as test results?

eraserhd19:03:04

As in, "expected: 42, got: #error { ... 8000 lines ... }"?

ddeaguiar19:03:22

you got the error as a response body?

ddeaguiar19:03:40

my comment was about log file noise

eraserhd19:03:07

Yeah, I'm not looking at the logs. The error is an exception thrown from io.pedestal.test/response-for

eraserhd19:03:33

The test runner prints it at the REPL, which is painful.

ddeaguiar19:03:06

I’m not sure of what the best solution is there other than setting the max stack trace depth at jvm startup