How about creating a group "regress", and we can move them into tests/regress for better categorization, for regression tests? And for tests that attempt find new problems, we already have a group "fuzzers"; and perhaps there should be a some standard guieline for how long a single invocation of a fuzz test should run before quitting. I'd say something in the 5 to 15 minute range? People can always run the fuzz test multiple times, and if the fuzz test can save test between runs, it should matter that it's broken up into multiple test invocations. - Ted
