Version 1 (modified by Nicklas Nordborg, 16 years ago) ( diff )

Adding test protocol for minor release

Minor release test protocol

This 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.

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.

In the table below the following notation is used:

  • 2.N = the BASE version that is to be released
  • 2.P = the last patch release of the previous version
  • initdb/updatedb = run the installation/upgrade script
  • TestAll = run the TestAll test program
  • test roles = run the roles test program as described in doc/test/roles/index.html

Automated tests

MySQL PostgresSQL
1. Basic installation of 2.N
a) initdb
b) TestAll
c) test roles
2. Upgrade a fresh installation
a) initdb (on 2.P)
b) updatedb (on 2.N)
c) TestAll (on 2.N)
3. Upgrade an installation with data
a) initdb (on 2.P)
b) test roles (on 2.P)
c) updatedb (on 2.N)

Manual tests

Manual testing of different user roles using the web interface. Follow the instructions in the doc/test/roles/index.html document.

Firefox Internet Explorer
a) root user
b) administrator
c) power user
d) user
e) guest
Note: See TracWiki for help on using the wiki.