There is an opening in my QA department at Red Hat. Note, the posting
below is a somewhat generic and does not mention Clojure, but I can tell
you that Clojure is already being used extensively by our group, and that
you would be using it regularly.
I am using clojure for functional testing ('functional' as opposed to unit
testing, I don't mean in the FP sense).
My tests write a clojure-formatted file containing all the test results.
Each result may include:
1) The code of the test
2) Parameters of a data-driven test
3) Trace of a failed
I wish there was a built-in for this as well. I don't know that
(constantly) is a good name for it though. I couldn't think of a good
name, apparently a null function means the same as identity function so
that doesn't work.
On Monday, April 2, 2012 2:39:31 PM UTC-4, Jay Fields wrote:
I
I believe the latest code does capture closures properly. I haven't tested
all kinds of crazy corner cases, but it does work for all my closures.
From browsing git, it looks like the project.clj version hasn't been
incremented in 7 months, and the fix for closures came in after that. If
I use serializable.fn pretty extensively, and it's been working great for
me. I think at this point, the only fix I put in that Phil didn't is that
my serialized fn's print with an unqualified fn symbol, instead of
serializable.fn/fn. I did that so it's more readable, the tradeoff is
that if
