For developers of database drivers it might be extremely important to allow the running of eunit and common test suites against a particular database driver.
Rebar3 already allows running a single test suite, but now the fmke_core_unit_test_SUITE suite runs unit tests for every supported database. What we need to do is export the common functionality into a separate module, then dissolve fmke_core_unit_test_SUITE and create a suite for each database and each data model implementation. Inside each database test suite will be several calls to the previously separated module.
This will allow driver developers to test their implementations on database X by running:
For developers of database drivers it might be extremely important to allow the running of eunit and common test suites against a particular database driver.
Rebar3 already allows running a single test suite, but now the
fmke_core_unit_test_SUITEsuite runs unit tests for every supported database. What we need to do is export the common functionality into a separate module, then dissolvefmke_core_unit_test_SUITEand create a suite for each database and each data model implementation. Inside each database test suite will be several calls to the previously separated module.This will allow driver developers to test their implementations on database X by running:
It would make sense that the common code allows for an easy launch of a docker image, to also simplify the code of each database test suite.