Bug 9724

Summary: Create a YP 2.4 test plan for package upgrades
Product: [QA/Testing] Test Plans/Suite Reporter: Joshua Lock <joshuagloe>
Component: test-plans/suiteAssignee: Libertad <libertad.gonzalez.de.la.cruz>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: alejandro.hernandez, anibal.limon, corneliux.stoicescu, jose.perez.carranza, sonia.delgado
Version: unspecified   
Target Milestone: 2.4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)
Bug Depends on: 9675    
Bug Blocks: 11483    

Description Joshua Lock 2016-06-07 15:47:41 UTC 
It would be very nice if people building distributions which make use of package managers could upgrade their devices between distribution revisions which cross YP release boundaries, i.e. upgrading from a Jethro based distro to a Krogoth based distro.

To help ensure that this is possible we need to design automated QA tests which validate the upgrade path for each package manager we support.

There are likely to be several challenges here, not least of all that we'll need to maintain a baseline state which the upgrade is tested from (previous state and previous release being the two obvious ones).

I've added #9675 to the "Depends on" because we shouldn't invest too much time in this until a decision has been made on the future of SmartPM, etc.
Comment 1 Benjamin Esquivel 2016-06-07 17:15:07 UTC 
Looks like a good thing to do, this would also be a documentation change, to list instructions for making the upgrade. Update from previous revision and state (like you mentioned Joshua) would make a viable scope for testing.
Comment 2 Sonia Delgado 2017-01-23 16:29:20 UTC 
I'm moving this to M4 at it depends on 9675 which is targeted for 2.3 M4
Comment 3 Libertad 2017-05-08 22:28:21 UTC 
I have created 14 testcases held withing the following testplan

https://bugzilla.yoctoproject.org/tr_show_plan.cgi?plan_id=207
Comment 4 Libertad 2017-06-26 15:46:12 UTC 
Test cases were executed on 2.4 cycle