Fork me on GitHub
#clojure
<
2016-07-24
>
richiardiandrea00:07:34

I would exclude that (95%) as I am using boot with-cp -s exatly to avoid that...it looks like it is more of a ex-info problem though, because I am not sure clojure.logging knows how to print an ex-info, I am actually going to check the source, it is better than guessing 😄

stuartsierra16:07:40

@richiardiandrea: It's likely not caused by anything in clojure.tools.logging but rather the underlying logging implementation and how it prints exceptions. Some logging implementations (java.util.logging for example) will print Exceptions by calling .toString(); some (Logback for example) use .getMessage() instead.

richiardiandrea16:07:23

@stuartsierra: thanks for sharing, I think this is the missing piece, I am using Log4j2 at the moment and I saw that Clojure.logging as you said just retrieves the logger instance

richiardiandrea16:07:15

So I guess it is not calling toString for ERROR

paulspencerwilliams16:07:09

Hey all. Having spent some time yak shaving with Cucumber testing clojure apps, it would appear that it’s so low-used within our community that I might be better investigating other libraries / frameworks / approaches that support acceptance / integration testing. What do you use?

roberto16:07:34

clojure.test ftw 🙂

akiva16:07:00

@paulspencerwilliams, a lot of people just stick with the official clojure.test. It’s battle-tested, hardy, and decidedly less fancy than the alternatives. I personally really like Jay Fields’ Expectations because it’s highly flexible and deliciously minimalist. And people tend to have a love-it-or-hate-it opinion on Midje.

akiva16:07:49

I do everything in clojure.test these day mainly because it’s mostly widely adopted and it does get out of my way.

roberto16:07:10

yeah, I don’t want to invest time in learning another testing framework. clojure.test is simple enough and does the job. I have testing framwork fatigue and js tooling fatigue 🙂

paulspencerwilliams17:07:27

So plain clojure.test tests with abstractions of the web UI, and database connectivity for clean up etc?

akiva17:07:58

Not sure what you mean by ‘database connectivity for clean up’.

paulspencerwilliams17:07:45

Sorry, so cleaning up app state after each test run for the next test.

akiva17:07:27

Honestly, if I’m testing, I do it all in isolation. Once you involve a database or whatever, you’re not unit testing anymore, it’s integration.

paulspencerwilliams17:07:59

@akiva: agreed, I do most testing with isolation, but I've always relied on a set of integration tests to ensure all the units work together.

wei19:07:15

In this component example, there’s a dummy message broker. https://github.com/stuartsierra/component/blob/master/dev/user.clj How would you actually implement this message broker?

wei19:07:41

Perhaps a core.async pubsub?

lmergen19:07:21

There are literally hundreds of different ways to implement a message broker, so it's difficult to give a good answer without knowing any context.