in reply to examples in test suite

I've been thinking about this sort of thing, but not for modules. When we write about Perl, we embed code in the text. How do we check that the code still works? It may have worked when I put it in there, but the spellchecker, search-and-replace, and all sort of other things can change it. We might even change it thinking it's a small change we don't need to test.

I haven't figured out the solution, but I think it might be Template Toolkit like Dave Cross explained in . All the code samples live in their own files, and have test files to check them. When we want to assemble the final version, something goes through all the code, tests it, inserts it in the right places, and so on. It could also auto-number the examples.

That's as far as I've thought about it because I haven't had time to do anything about it while I'm in the middle of projects that already do things some other way.

--
brian d foy <bdfoy@cpan.org>