Comment 10 for bug 1528583

I've redone the basic smoke testing for verifying just the package upgrades.
No issues were found during testing.

These tests do not include full Ubuntu release upgrades; They were only run on
16.04.

To include 5.5 I rebuilt it from the current 5.5.47 source in Debian. The 5.6
packages were used from the main Ubuntu repository, and the 5.7 packages were
installed from the ppa at
https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mysql-5.7

For each test I added minimal database data. One table with a couple of rows
and a test user with a password.

I ran through each test both with and without setting a password for the root
user.

For each test I verified that:

* mysql_upgrade was run successfully during installation (except for the clean
 install.
* If the root user had a password that the password was still valid
* If the root user had a blank password that the auth_socket plugin was enabled,
 requiring host system root access to log in with it.
* That the test user login was still valid
* That the test table data was intact

Upgrade paths tested:

* Fresh 5.7 install
* 5.7 installed on existing 5.7 database
* Fresh 5.6 install, upgraded to 5.7
* Fresh 5.5 install, upgraded to 5.7
* Fresh 5.5 install, upgraded to 5.6, then upgraded to 5.7
* Fresh 5.5 install, upgraded to 5.6, mysql_upgrade run, then upgraded to 5.7

We'll move on to more comprehensive upgrade testing including a full test
database and Ubuntu release upgrades.