Thanks Colin
I probably should've added that this is a large enterprise doing what's
essentially an in-house startup - building an app using Clojure. The app
initially sat somewhat off to the side of the corporation's main line of
business, but there was always the intent to incorporate the
Thanks Linus,
You make a really good point - why can't testers use the REPL? I'd like to
think that was possible too - after all, *I* can do it so why can't anyone
else?
That said, I'm slightly blessed in that I've done a lot of work in Erlang
and R over many years, so I was already
I really cant see how the testers could NOT be able to use a repl to do
some exploratory testing.
Clojure's strength is really that you can align the code very closely to
the domain, although this modelling is (as always) challenging.
And the application logic does not have to be tested through
Hi David,
Not to overstep the implied etiquette of these situations/patronise or
condescend(!), but reading between the lines, I don't think you have a
technology constraint I think you have a process constraint. You dropped
the word agile in there (which is usually a license for people to
I also meant to say that it is worth doing a cost-benefit analysis on
testing. When I did my consultant thing I frequently saw massive investment
in tools, process, emotion(!) etc. in things that on paper were a good
thing but in reality weren't mitigating any real risk.
All testing isn't
Hi David,
Your post is very technology orientated (which is fine!). Have you looked
into BDD type specifications? I am talking specifically the process
described in http://specificationbyexample.com/. If you haven't, I strongly
recommend you do as the win in this situation is they separate the
Hi Colin
Thanks for your reply.
My post is almost exclusively technology oriented because I think the
technology is what's killing us!
We've got what you'd probably call BDD lite working, in that we've got a
mutant form of agile process running whereby we work in 2 week sprints, but
there's
On our non-trivial application, we have broken our testing into the
following sets:
* Unit Tests -- written by devs, run as part of our integration builder and
when doing dev
* Integration Tests -- automated, hitting our external APIs, written in
clojure, maintained by the devs mostly, run as
