There are certain tests in my distribution that I don't want end users to run. I want to run them during development, and I also want anyone else contributing to the distribution to run them. These are typically related to static analysis of the code, e.g. perl critic, perl tidy and pod checking - it makes no sense to risk having these fail for end users.

Is there a standard for signifying internal-only tests, and for make test to figure out when they should run?

Jon

Reply via email to