[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: BDD testing framework without dependencies
- From: steve donovan <steve.j.donovan@...>
- Date: Tue, 23 Aug 2016 08:30:57 +0200
On Tue, Aug 23, 2016 at 8:11 AM, Sean Conner <firstname.lastname@example.org> wrote:
> And still I ask---what does a framework buy you that assert() doesn't?
> Other than (in my opinion) excessive overhead on a possibly buggy framework?
Just a few little helpers go a long way. My favourite of course is
pl.test (164 lines) because I really didn't want an external test
dependency. That's how the rot starts, of course. I am also a little
bemused by the fetishization of over-complicated test harnesses.
Clearly this is a wheel that needs to be constantly re-invented.
What IMHO is more important than the testing framework itself is
writing clear tests which might actually be useful to outsiders. I
know the mantra is 'tests are documentation' but this is not
automatically true, no more than wikis spontaneously organizing