Test server usage

The table below lists, for each package, which database testing servers it uses as part of its unit tests.

• T means the package uses the database server for testing
• X means the package does not use the database server for testing
• An empty cell means the package does not directly talk to the database

Package	PostgreSQL	SQL Server	Oracle	Redshift	Snowflake	Spark	BigQuery	SQLite
Achilles	T	T	T	T	X	X	X	X
Andromeda
BigKnn
BrokenAdaptiveRidge
Capr	X	X	X	X	X	X	X	T
Characterization	X	X	X	X	X	X	X	T
CirceR
CohortDiagnostics	T	T	T	T	X	X	X	T
CohortExplorer	T	T	T	T	X	X	X	X
CohortGenerator	T	T	T	T	X	X	X	T
CohortMethod	T	X	T	X	X	X	X	T
Cyclops
DatabaseConnector	T	T	T	T	T	T	T	T
DataQualityDashboard	T	T	T	T	X	X	X	T
DeepPatientLevelPrediction	X	X	X	X	X	X	X	T
EmpiricalCalibration
EnsemblePatientLevelPrediction
Eunomia	X	X	X	X	X	X	X	T
EvidenceSynthesis
FeatureExtraction	T	T	T	T	X	X	X	T
Hydra	X	X	X	X	X	X	X	T
IterativeHardThresholding
MethodEvaluation	X	X	X	X	X	X	X	T
OhdsiSharing
OhdsiShinyModules	T	X	X	X	X	X	X	T
ParallelLogger
PatientLevelPrediction	T	X	X	X	X	X	X	T
PhenotypeLibrary
PheValuator	X	X	X	X	X	X	X	T
ResultModelManager	T	X	X	X	X	X	X	T
ROhdsiWebApi
SelfControlledCaseSeries	T	X	X	X	X	X	X	T
SelfControlledCohort	T	T	T	T	X	X	X	T
ShinyAppBuilder	X	X	X	X	X	X	X	T
SqlRender

This table was constructed simply by looking for the environmental variable names of the test server credentials in each package’s test code, and may therefore not reflect actual testing. Whether a package connects to a database at all was determined by evaluating whether it imports DatabaseConnector.