mirror of
https://gitea.osmocom.org/cellular-infrastructure/osmo-hlr.git
synced 2025-10-23 00:12:14 +00:00
5b65461d68
We have a database schema upgrade path, but so far nothing that verifies that we don't break it. It almost seems like the user data weren't important to us!? Add a db upgrade test: - Create a db with an .sql dump taken from a db created with an old osmo-hlr, producing DB schema version 0. - Run osmo-hlr --db-upgrade --db-check - Verify that the upgrade exited successfully. - Verify that restarting with the upgraded DB works. If python tests are enabled, also: - create a new database using the new osmo-hlr (just built). - replay a VTY transcript to create subscribers as in the old snapshot. - replay some sql modifications as done in the old snapshot. - Get a list of sorted table names, - a list of their sorted columns with all their properties, - and dump the table contents in a column- and value-sorted way. - Compare the resulting dumps and error if there are any diffs. (This is how I found the difference in the imei column that was fixed in I68a00014a3d603fcba8781470bc5285f78b538d0) Change-Id: I0961bab0e17cfde5b030576c5bc243c2b51d9dc4
15 lines
380 B
Makefile
15 lines
380 B
Makefile
EXTRA_DIST = \
|
|
db_upgrade_test.sh \
|
|
db_upgrade_test.err \
|
|
db_upgrade_test.ok \
|
|
hlr_db_v0.sql \
|
|
osmo-hlr.cfg \
|
|
create_subscribers.vty \
|
|
$(NULL)
|
|
|
|
update_exp:
|
|
$(srcdir)/db_upgrade_test.sh $(srcdir) $(builddir) >"$(srcdir)/db_upgrade_test.ok" 2>"$(srcdir)/db_upgrade_test.err"
|
|
|
|
upgrade-equivalence-test:
|
|
$(srcdir)/db_upgrade_test.sh $(srcdir) $(builddir) do-equivalence-test
|