We currently have all DB adapters inside the Parse Server repository. We plan to move the adapters into separate repositories (or convert everything into a mono-repository), but that hasn’t happened yet. You are right that technically you’d want to run all the tests in Parse Server using the Oracle DB adapter. We don’t have a concept yet for how to do that.
The tests are specified to run for either MongoDB or Postgres. Even the test syntax is tailored to these 2 adapters, which allows to define to run a test for only a certain adapter or even a certain version of the adapter. Maybe we’d have to redesign the test syntax to be more adapter agnostic.
For example instead of adding the adapter definition to the test, the adapter could define which tests to run and which to ignore via a config file that is part of the adapter. Then the Oracle DB adapter could import Parse Server as a dev dependency, add itself as DB adapter and the tests would run according to the adapter’s config file. Just an idea, but again, there is no clear concept yet.
What would you like to communicate? Should people test the adapter, or what should be the call to action? Maybe we should solve the testing issue above first before we invite a lot of developers. And maybe let’s also try to address the license questions at some point which we talked about briefly some time ago, to bring more legal clarity for developers.