On Oct 3, 2006, at 11:04 PM, Adam Kennedy wrote:
I'd ideally like to keep this constrained to a single environment
variable.
These tests are all the same sort of thing, tests that you run
before you release, but not otherwise. If so, there's the existing
AUTOMATED_TESTING flag.
So that would give us two options, one for general bulk testing,
another for when releasing modules.
I like the simplicity.
OK, I can accept that. It sacrifices a small convenience for elegance.
Then my one remaining itch is your use of the term "release". These
tests are run frequently during development, not just at release
time. That's why I've been calling them author tests or developer
tests. Yes, they are often prereqs for release, but do we want to
tie them that intimately to release? After all, some modules never
get released...
I'd be much happier with a term that points at the development or
authoring process.
Chris
--
Chris Dolan, Software Developer, Clotho Advanced Media Inc.
608-294-7900, fax 294-7025, 1435 E Main St, Madison WI 53703
vCard: http://www.chrisdolan.net/ChrisDolan.vcf
Clotho Advanced Media, Inc. - Creators of MediaLandscape Software
(http://www.media-landscape.com/) and partners in the revolutionary
Croquet project (http://www.opencroquet.org/)
