[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Software testing in general, esp. Software Inspections (was: BDD testing framework...)
- From: Dirk Laurie <dirk.laurie@...>
- Date: Wed, 24 Aug 2016 08:44:14 +0200
2016-08-24 8:11 GMT+02:00 sur-behoffski <firstname.lastname@example.org>:
> This is perhaps a place where the easy-to-get-started nature of Lua,
> being able to hack scripts together quickly, and then mutate them as
> knowledge of the problem domain grows, is vulnerable to problems:
> There is no formal specification that the programmer is starting from.
My approach is:
1. Cobble some scripts together as you say.
2. Document them, but go a bit beyond, i.e. document also what
they don't yet.
3. Write the missing pieces, plus a few extra features.
4. Alternate between steps 2 and 3.
That way, either the documentation or the code is always no more
than about a week ahead of the other.