From pgilbert902 at gmail.com  Mon May  4 19:38:52 2015
From: pgilbert902 at gmail.com (Paul Gilbert)
Date: Mon, 04 May 2015 13:38:52 -0400
Subject: [Rd] Print output during long tests?
In-Reply-To: <CALK03d3j0uZh_YK9dP9kdZ6JVmO44=gSGe6_+7ikjk-uKm-JMA@mail.gmail.com>
References: <CALK03d3j0uZh_YK9dP9kdZ6JVmO44=gSGe6_+7ikjk-uKm-JMA@mail.gmail.com>
Message-ID: <5547AEAC.1000406@gmail.com>

If your tests can be divided into multiple files in the tests/ directory 
then you will get lines like

  * checking tests ...
  Running ?test1.R?
  Running ?test2.R?
  Running ?test3.R?
  ...

Paul

On 05/04/2015 11:52 AM, Toby Hocking wrote:
> I am the author of R package animint which uses testthat for unit tests.
>
> This means that there is a single test file (animint/tests/testthat.R) and
> during R CMD check we will see the following output
>
> * checking tests ...
> Running ?testthat.R?
>
> I run these tests on Travis, which has a policy that if no output is
> received after 10 minutes, it will kill the check. Because animint's
> testthat tests take a total of over 10 minutes, Travis kills the R CMD
> check job before it has finished all the tests. This is a problem since we
> would like to run animint tests on Travis.
>
> One solution to this problem would be if R CMD check could output more
> lines other than just Running testthat.R. Can I give some command line
> switch to R CMD check or set some environment variable, so that some more
> verbose test output could be shown on R CMD check?
>
> 	[[alternative HTML version deleted]]
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>



[Rd] Print output during long tests?
Paul Gilbert