expfactory / expfactoryr Goto Github PK

This should likely be a part of the expfactoryr library itself, since it's core functionality is also to test.

Error: ‘testthat’ >= 1.0.2 must be installed for this functionality.

@earcanal the library has other purpose as well, like to parse data? We should have a Docker entrypoint with different commands - I'll make "test" coincide with testing a package folder (and if there are other command line stuffs we can add/talk about after)

Currently, failed tests (from another CI environment) aren't getting through.

test_breath_counting.R:20: error: (unknown)
there is no package called ‘expfactoryr’
1: process_breath_counting(path, p = 1) at /data/expfactory.breathcounting/tests/testthat/test_breath_counting.R:20
2: expfactoryr::process_expfactory_experiment at /data/expfactory.breathcounting/R/expfactory.breathcounting.R:45
3: getExportedValue(pkg, name)
4: asNamespace(ns)
5: getNamespace(ns)
6: tryCatch(loadNamespace(name), error = function(e) stop(e))
7: tryCatchList(expr, classes, parentenv, handlers)
8: tryCatchOne(expr, names, parentenv, handlers[[1L]])
9: value[[3L]](cond)
────────────────────────────────────────────────────────────────────────────────

══ Results ═════════════════════════════════════════════════════════════════════
Duration: 0.4 s

OK:       1
Failed:   3
Warnings: 0
Skipped:  0
> 
> 
4. Grabbing man pages from container!

So dense!

hey @earcanal ! I'm developing some infrastructure for rOpenSci, and was wondering if I could use expfactoryr as a test package. It would mean adding it as a submodule to a repository, and then doing some trivial pushes / updates. Would that be okay with you?

@earcanal you can use the configuration at expfactory-experiments/state-mindfulness-survey#3 to get this setup. I can take care of connecting to CircleCI - could you please look at the error in the link about root install and help debug what we should try? What I'd like to do is:

1. Get that build setup here to build (and deploy) the expfactoryR container
2. Then use expfactoryR in that linked PR so we don't have to build it

hey @earcanal !

I'm testing a build, and I'd expect to be able to do:

R -e "library(expfactoryr); sessionInfo()"

but that doesn't work! Instead I have to do:

R -e "library(expfactory); sessionInfo()"

Is this intentional / the standard for most packages? if so, how do I reliably get the package name to load?