Compatibility

Tests Code

Part of the CD pipeline, compatibilities tests are runned against significant DBMS.

The script use official docker image for DBMS and latest (so just build) WebDB image to run. For DBMS, the script retrieve 150 latest docker tag and use the 5 unique digests to run test against

You can find tests sources here

Tests call API endpoint like the frontend would do and are written in the new bare Node.js test framework

Tests produce results in JUnit format, so you can see with a traditionnal viewer

Results

However, I didn't find any tool adequate for the special need of WebDB use case so I develop mine

The results you see here are the unit test download from gitlab artifact and transform to be quite synthetic, group by DBMS, tag and subject

Execution duration are not accurate because scripts had to wait for API call before continuing

DBMS

Test are very time consuming, whether it's for server or development, so only popular DBMS are tested

You can consider that test of major DBMS can be mainly transpose for other compatible ones

For example, Percona MySQL is almost totally compatible with Oracle MySQL, so tests and results will be also. However, keep in mind that I used "mainly" so do not consider 100% compatibility, for example you will see differences between Percona and Oracle while you shouldn't. This is because small changements between forks can be detected in tests

Last updated