From pgilbert902 at gmail.com  Mon Sep 22 17:25:57 2014
From: pgilbert902 at gmail.com (Paul Gilbert)
Date: Mon, 22 Sep 2014 11:25:57 -0400
Subject: [Rd] extra package tests directory
Message-ID: <54203F85.1090701@gmail.com>

I am trying to decide on a name for a directory where I will put some 
extra package tests. The main motivation for this is the need to limit 
the package test time on CRAN. That is, these are tests that could be in 
the tests/ directory and could be run on CRAN, but will take longer than 
CRAN likes.

Scanning through names currently being used in packages on CRAN I see a 
large number of inst/tests/ directories, but they seem to be instead of 
a tests/ directory at the top level of the package. (There are also some 
occurrences of inst/test and test/ at the top level.) I would prefer not 
to use these directories as I don't like the possible confusion over 
whether these are the standard package tests or additional ones.

The other name that is used a fair amount is inst/unitTests/ (plus 
inst/UnitTests/, plus inst/UnitTest/, plus inst/unittests).  In many 
case these seem to be run by a script in the tests/ directory using a 
unit testing framework, so they cannot easily be distinguished from the 
normal package tests/ run by CRAN.

I see also an occurrence each of inst/otherTests/ inst/testScripts/ and 
inst/test_cases.

My own preference would be inst/extraTests but no one is using that.

Have I missed anything? Does anyone have suggestions or comments? Are 
there other reasons one might want tests that are not usually run by CRAN?

Paul



[Rd] extra package tests directory
Paul Gilbert