[MXS-51] Create functional package upgrade tests Created: 2015-03-19  Updated: 2016-03-09  Resolved: 2016-02-10

Status: Closed
Project: MariaDB MaxScale
Component/s: test
Affects Version/s: None
Fix Version/s: 1.4.0

Type: Task Priority: Major
Reporter: Kolbe Kegel (Inactive) Assignee: Timofey Turenko
Resolution: Fixed Votes: 0
Labels: None

Sprint: 1.4.0-1, 1.4.0-2, 2016-3

 Description   

There should be tests to ensure that upgrades to new MaxScale packages work as expected (see MXS-49 and MXS-50 for why this is important).

Here are some ideas about what should be tested:

1. Make sure the upgrade is successful
2. Make sure the service starts after upgrade
3. Make sure the service stops after upgrade
4. Make sure the new package can be removed without problem
5. Make sure the new package can be installed again without problem
6. Make sure the package can be downgraded to the previous release

Maybe there are more?

 Comments   
Comment by Dipti Joshi (Inactive) [ 2015-05-02 ]

tturenko, Please estimate the effort level and update the Original Estimate field.

Comment by Timofey Turenko [ 2015-05-15 ]

"maxscale_update_test_all/" Jenkins job added.
Result analysis improvement is still needed, but it will be implemented after move to Vegrant setup.

Comment by Dipti Joshi (Inactive) [ 2016-01-26 ]

johan.wikman tturenko I see that the regular release prep related testing tasks that were created for 1.3, we are putting them in 1.4.x sprints. Please create new tasks for 1.4.0 release and close 1.3.0 related testing tasks - so that we have proper history of tasks for 1.3 vs. 1.4

Comment by Johan Wikman [ 2016-01-26 ]

dshjoshi We have only one sprint in which 1.3 testing and 1.4 development takes place. If there is a mistake, it's having 1.4 in the name of the sprint.

Generated at Thu Feb 08 03:56:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.