Sandeep Sukhani a9c327c068 [MM-13341] Add an upgrade test to verify schema (#10419) ...

* [MM-13341] Add an upgrade test to verify schema

Upgrade test is done by following steps:
1. A mysql dump generated from v4.10.0 is imported in a database and is ran through migration code
2. Another fresh database is generated without any initial data, which gets latest schema.
3. Diff between these 2 databases is generated using mysqldiff tool from mysql utilities

For db setup, version cli command is used which takes care of migration or setup of fresh db

* Using 5.7 tag for mysql docker image which is already used for db setup

* Starting docker containers for db before running tests

* Using db from v5.0.0 for migration test

* Added migration test for psql and made some improvements in running commands in docker

* Add postgres db dump file

* Updated message

* moved dump files to scripts and using error code from diff command

2019-03-19 15:05:15 -04:00

..

ldap-check.sh

Adding a script to help with ldap config issues (#7995)

2018-01-02 12:11:30 -08:00

license-check.sh

Move file backend to its own service (#9435)

2018-09-20 10:07:03 -07:00

mattermost-mysql-5.0.sql

[MM-13341] Add an upgrade test to verify schema (#10419)

2019-03-19 15:05:15 -04:00

mattermost-postgresql-5.0.sql

[MM-13341] Add an upgrade test to verify schema (#10419)

2019-03-19 15:05:15 -04:00

mysql-migration-test.sh

[MM-13341] Add an upgrade test to verify schema (#10419)

2019-03-19 15:05:15 -04:00

prereq-check.sh

update go to 1.12 (#10382)

2019-03-01 12:55:35 -05:00

psql-migration-test.sh

[MM-13341] Add an upgrade test to verify schema (#10419)

2019-03-19 15:05:15 -04:00

test-xprog.sh

Make test execution not take quadratic compilation time (#7610)

2017-10-12 08:35:19 -07:00

test.sh

unittest using externally managed database (#9400)

2018-12-10 17:58:09 +01:00