Changes between Version 13 and Version 14 of MinorReleaseTest


Ignore:
Timestamp:
Aug 11, 2021, 8:50:58 AM (16 months ago)
Author:
Nicklas Nordborg
Comment:

Remove tests related to MySQL

Legend:

Unmodified
Added
Removed
Modified
  • MinorReleaseTest

    v13 v14  
    33This protocol lists the tests that should be performed before a minor release (eg. a release that changes the second version number). Patch releases (that changes the third number) doesn't have to go through the tests.
    44
    5 The tests should make sure that a basic installation/upgrade is working on MySQL and on PostgreSQL. This part is done with an automated test program. A second part is a manual test of web interface that includes most of the major features of BASE. These tests should be done about a week before the scheduled release to make sure that there is enough time to fix any problems. During the last week it is of course not allowed to make any changes in the code that will fundamentally change the results of the test. For example, do not change the database.
     5The tests should make sure that a basic installation/upgrade is working on PostgreSQL.
     6Since BASE 3.19 we do not test with MySQL. This part is done with an automated test program. A second part is a manual test of web interface that includes most of the major features of BASE. These tests should be done about a week before the scheduled release to make sure that there is enough time to fix any problems. During the last week it is of course not allowed to make any changes in the code that will fundamentally change the results of the test. For example, do not change the database.
    67
    78In the table below the following notation is used:
     
    1213  * `TestAll` = run the `TestAll` test program
    1314  * `test roles` = run the roles test program as described in [/chrome/site/latest/test/roles/index.html latest/test/roles/index.html]. This test program can also use batch importers instead of the hard-coded item creation. Use this mode with either MySQL or PostgreSQL and the normal mode with the other. Run in batch-import mode with `./test.sh roles -b all`
    14   * MySQL ► PostgreSQL migration can be tested with the MySQL database from 1c. A new database is needed on the PostgreSQL side. Migration is not possible in the PostgreSQL ► MySQL direction.
    1515
    1616== Automated tests ==
    1717
    18 ||                                               || ''' MySQL ''' || ''' PostgresSQL ''' ||
    19 || '''1. Basic installation of 3.N'''            ||    -----      ||      -----          ||
    20 || a) `initdb`                                   ||               ||                     ||
    21 || b) `TestAll`                                  ||               ||                     ||
    22 || c) `test roles`                               ||  -b           ||                     ||
    23 || '''2. Upgrade a fresh 3.P installation'''     ||    -----      ||      -----          ||
    24 || a) `initdb` (on 3.P)                          ||               ||                     ||
    25 || b) `updatedb` (on 3.N)                        ||               ||                     ||
    26 || c) `TestAll` (on 3.N)                         ||               ||                     ||
    27 || '''3. Upgrade a 3.P installation with data''' ||    -----      ||      -----          ||
    28 || a) `initdb` (on 3.P)                          ||               ||                     ||
    29 || b) `test roles` (on 3.P)                      ||               ||                     ||
    30 || c) `updatedb` (on 3.N)                        ||               ||                     ||
    31 || '''4. Migration MySQL ► PostgreSQL on 3.N'''  ||    -----      ||      -----          ||
    32 || a) `migrate export`                           ||               ||         N/A         ||
    33 || b) `migrate import`                           ||      N/A      ||                     ||
     18||                                               || ''' PostgresSQL ''' ||
     19|| '''1. Basic installation of 3.N'''            ||      -----          ||
     20|| a) `initdb`                                   ||                     ||
     21|| b) `TestAll`                                  ||                     ||
     22|| c) `test roles`                               ||                     ||
     23|| '''2. Upgrade a fresh 3.P installation'''     ||      -----          ||
     24|| a) `initdb` (on 3.P)                          ||                     ||
     25|| b) `updatedb` (on 3.N)                        ||                     ||
     26|| c) `TestAll` (on 3.N)                         ||                     ||
     27|| '''3. Upgrade a 3.P installation with data''' ||      -----          ||
     28|| a) `initdb` (on 3.P)                          ||                     ||
     29|| b) `test roles` (on 3.P)                      ||                     ||
     30|| c) `updatedb` (on 3.N)                        ||                     ||
    3431
    3532