> On the other hand, the test completes successfully if I manually execute it line-by-line, but this is not feasible in practice because there are 21 sets of tests. > 3: predict.asreml(asreml.obj, classify = classify, sed = pairwise, trace = trace. > 2: predict(asreml.obj, classify = classify, sed = pairwise, trace = trace. > wald.tab = current.asrt$wald.tab, present = c("Type", "Species", "Sources")) at testthat/testPredictionsPresentation.r:17 > 1: predictPlus.asreml(classify = "Sources:Type", asreml.obj = current.asr, tables = "none", > However, if I do this in the code then the suite of unit tests that I have for asremlPlus fails when run with testthat::test_check with the following Error: In spite of this it is possible to call them using summary, fitted and predict. > Now asreml has three functions summary.asreml, fitted.asreml and predict.asreml that are (i) not exported and (ii) not declared to be S3 methods. > Suggests or Enhances not in mainstream repositories: It is not available in a public repository and because of this, when checking it for CRAN, it always gives the following NOTE, which is acceptable to CRAN: > I have a package asremlPlus that "Enhances" the commercial package asreml (and asreml4), for which I am not a maintainer. Next message (by thread): Problem enhancing a package with a predict method not declared to be an S3 method.Previous message (by thread): Problem enhancing a package with a predict method not declared to be an S3 method.Problem enhancing a package with a predict method not declared to be an S3 method Duncan Murdoch murdoch.duncan at Problem enhancing a package with a predict method not declared to be an S3 method
0 kommentar(er)
