Ideas for testers (what needs testing?)

Steve Holton sph0lt0n at
Thu May 8 16:57:09 EDT 2008

On Thu, May 8, 2008 at 4:19 PM, Martin Langhoff <martin.langhoff at>

> On Fri, May 9, 2008 at 4:17 AM, Steve Holton <sph0lt0n at> wrote:
> > It seems a recipe for dumping the designers into the hell of constantly,
> > interactively  explaining to the testers what was expected, what wasn't,
> and
> > why.
> It's not *that* bad ;-) Explore it, figure it out - after all, that's
> what we expect our end users to do! - and of needed, ask the original
> designers and developers for some explanation (that can hopefully be
> captured in the wiki as documentation).
> This approach has worked fantastic for Moodle and other projects. The
> alternative is to line up an army of technical writers, and I've only
> heard of one around here so far...

That seems to be the case.  And it's hard to argue with success.
As long as nobody is going to get upset when I test, then I suppose I'll be
as happy as a clam.

Steve Holton
sph0lt0n at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Devel mailing list